View XRT84L38-L38PCI_2187633.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

exar corporation 48720 kato road, fremont ca, 94538 ? (510) 668-7000 ? fax (510) 668-7017 ? www.exar.com xrt84l38 octal t1/e1/j1 framer september 2006 rev. 1.0.1 general description the xrt84l38 is an eight-channel 1.544 mbit/s or 2.048 mbit/s ds1/e1/j1 framing controller. the xrt84l38 contains an integrated ds1/e1/j1 framer which provides ds1/e1/j1 framing and error accumulation in accordance with ansi/itu_t specifications. each framer has its own framing synchronizer and transmit-receive slip buffers, and can be independently enabled or disabled as required and can be configured to frame to the common ds1/e1/j1 signal formats each framer block contains its own transmit and receive t1/e1/j1 framing function including 3 hdlc controllers to support v5.2. each transmit hdlc controller encapsulates contents of the transmit hdlc buffers into lapd message frames. each receive hdlc controller extracts payload content of receive lapd message frames from the incoming t1/e1/j1 data stream and writes it into the receive hdlc buffer. each framer also contains a transmit and overhead data input port, which permits data link terminal equipment direct access to the outbound t1/e1/j1 frames likewise, a receive overhead output data port permits data link terminal equipment direct access to the data link bits of the inbound t1/e1/j1 frames. the xrt84l38 fully meets all of the latest t1/e1/j1 specifications: ansi t1/e1.107-1988, ansi t1/ e1.403-1995, ansi t1/e1.231-1993, ansi t1/ e1.408-1990, at&t tr 62411 (12-90) tr54016, and itu g-703, g.704, g706 and g.733, at&t pub. 43801, and ets 300 011, 300 233, jt g.703, jt g.704, jt g706, i.431. extensive test and diagnostic functions include loop-backs, boundary scan, pseudo random bit sequence (prbs) test pattern generation, performance monitor, bit error rate (ber) meter, forced error insertion, and lapd unchannelized data payload processing according to itu-t standard q.921. applications and features (next page) f igure 1. xrt84l38 8- channel ds1 (t1/e1/j1) f ramer performance monitor prbs generator & analyser hdlc (lapd) controller & 96-byte buffer liu & loopback control dma interface signaling & alarms jtag wr ale_as rd rdy_dtack channel select a[6:0] d[7:0] interrupt memory microprocessor interface intel/motorola p configuration, control & status monitor 4 3 tx serial clock rx serial clock 8khz sync osc back plane 1.544-16.384 mbit/s local pcm highway st-bus 2-frame slip buffer elastic store tx serial data in tx encoder liu interface 2-frame slip buffer elastic store rx encoder liu interface rx framer rx serial data out rxpos 8 rxneg 8 rxlineclk 8 txpos 8 txneg 8 txlineclk 8 external data link controller tx overhead in rx overhead out xrt84l38 1 of 8-channels tx framer llb lb 8 8 tpos tneg tclk1 rpos rneg rclk1 p interface tx1 rx1 rx8 tx8 8-ch t1/e1/liu host mode xrt83l38 twisted pair twisted pair system (terminal) side line side 8 ds1/e1 channels 1.544/2.048 mhz
xrt84l38 2 octal t1/e1/j1 framer rev. 1.0.1 applications ? high-density t1/e1/j1 interfaces for multiplexers, switches, lan routers and digital modems ? sonet/sdh terminal or add/drop multiplexers (adms) ? t1/e1/j1 add/drop multiplexers (mux) ? channel service units (csus): t1/e1/j1 and fractional t1/e1/j1 ? digital access cross-connect system (dacs) ? digital cross-connect systems (dcs) ? frame relay switches and access devices (frads) ? isdn primary rate interfaces (pra) ? pbxs and pcm channel bank ? t3 channelized access concentrators and m13 mux ? wireless base stations ? atm equipment with integrated ds1 interfaces ? multichannel ds1 test equipment ? t1/e1/j1 performance monitoring ? voice over packet gateways ? routers features ? eight independent, full duplex ds1 tx and rx framers ? two 512-bit (two-frame) elastic store, pcm frame slip buffers (fifo) on tx and rx provide up to 8.192 mhz asynchronous back plane connections with jitter and wander attenuation ? supports input pcm and signaling data at 1.544, 2.048, 4.096 and 8.192 mbits. also supports 4-channel multiplexed 12.352/16.384 (hmvip/h.100) mbit/s on the back plane bus ? programmable output clocks for fractional t1/e1/j1 ? supports channel associated signaling (cas) ? supports common ch annel signalling (ccs) ? supports isdn primary rate interface (isdn pri) signaling ? extracts and inserts robbed bit signaling (rbs) ? 3 independent hdlc controllers for receive and transmit on a per channel basis ? each hdlc controller contains two 96-byte buffers ? timeslot assignable hdlc ? v5.1 and v5.2 interface ? 8-bit intel/motorola p and mips power pc interfaces for configuration, control and status monitoring ? parallel search algorithm for fast frame synchronization ? wide choice of t1 framing structures: d4, esf, slc ? 96, tidm and n-frame (non-framing) ? direct access to d and e channels for fast transmission of data link information ? prbs and qrss generation and detection
xrt84l38 3 rev. 1.0.1 octal t1/e1/j1 framer ? programmable interrupt output pin ? supports programmed i/o, burst and dma modes of read-write access ? each framer block encodes and decodes the t1/e1/j1 frame serial data into and from the single-rail or dual-rail (b8zs) format ? dual or single rail line side digital pcm inputs ? detects and forces red (sai), yellow (rai) and blue (ais) alarms ? detects oof, lof, los errors and cofa conditions ? loopbacks: local (llb) and line remote (lb) ? facilitates inverse multiplexing for atm ? performance monitor with one second polling ? boundary scan (ieee 1149.1) jtag test port ? accepts external 8khz sync reference ? 3.3v cmos operation with 5v tolerant inputs ? 388-pin bga package with ?40 c to +85 c operation ? direct interface to exar?s xrt83l38 (octal) liu ordering information p art n umber p ackage o perating t emperature r ange xrt84l38ib 388 pin plastic ball grid array -40 c to +85 c
xrt84l38 4 octal t1/e1/j1 framer rev. 1.0.1 f igure 2. p in o ut of the xrt84l38 t op v iew ( see pin list for names and function ) a b c d e f g h j k l m n p r t u v w y aa ab ac ad ae af 21 22 19 20 23 24 25 26 1 2 3 4 5 6 7 8 17 18 13 14 15 16 9 10 11 12 xrt84l38 (see pin list for pin names and function) top view ac 1 af 1 ae 1 ad 1 a1 d4 c1 b1 e1 f1 g1 h1 j1 k1 l1 m1 aa 1 ab 1 u1 v1 w1 y1 n1 p1 r1 t1 a 26 d 23 d 26 ac 23 ac 26 af 26 l 26 t 26 l 23 t 23 l 24 t 24 l 25 t 25 ac 4 d4 l4 l2 t2 l3 t3 t4 v3 v1 v1 v1 v1 g v1 v1 g g g g g g g g g g g v2 g g v1 v1 v3 v3 v3 v3 v3 v2 v2 v2 v2 v2 v2 v2
xrt84l38 i rev. 1.0.1 octal t1/e1/j1 framer table of contents general description................................................................................................ 1 f igure 1. xrt84l38 8- channel ds1 (t1/e1/j1) f ramer ............................................................................................................ 1 a pplications ............................................................................................................................... ............... 2 f eatures ............................................................................................................................... ..................... 2 ordering information ........................................................................................................... ........ 3 f igure 2. p in o ut of the xrt84l38 t op v iew ( see pin list for names and function ) ............................................................ 4 table of contents ..................................................................................................... i t able 1: l ist by p in n umber .............................................................................................................................. ........................... 5 pin descriptions ......................................................................................................... 5 t ransmit s erial d ata i nput ...................................................................................................................... 5 o verhead i nterface ............................................................................................................................... 14 r eceive s erial d ata o utput .................................................................................................................. 16 r eceive d ecoder l iu i nterface ............................................................................................................. 23 t ransmit e ncoder l iu i nterface ........................................................................................................... 23 t iming ............................................................................................................................... ........................ 24 l iu c ontrol ............................................................................................................................... .............. 25 jtag........................................................................................................................... .............................. 26 m icroprocessor i nterface .................................................................................................................... 27 p ower s upply p ins ............................................................................................................................... .. 30 g round p ins ............................................................................................................................... ............. 30 n o c onnect p ins ............................................................................................................................... ...... 31 e lectrical c haracteristics ................................................................................................................... 32 a bsolute m aximums ............................................................................................................................... . 32 dc e lectrical c haracteristics ............................................................................................................. 32 t able 2: xrt84l38 p ower c onsumption .............................................................................................................................. ... 32 1.0 microprocessor interface block ......................................................................................... 33 t able 3: c/p s election t able .............................................................................................................................. .................. 33 1.1 channel selection within the framer ........................................................................................ ...... 34 t able 4: c hannel s election .............................................................................................................................. ........................ 34 f igure 3. s implified b lock d iagram of the m icroprocessor i nterface b lock .................................................................... 35 1.2 the microprocessor interface block signal .............................................................................. 35 t able 5: xrt84l38 m icroprocessor i nterface s ignals that exhibit constant roles in both the i ntel and m otorola m odes 35 t able 6: i ntel mode : m icroprocessor i nterface s ignals ...................................................................................................... 36 t able 7: m otorola m ode : m icroprocessor i nterface s ignals ............................................................................................. 36 1.3 interfacing the xrt84l38 to the local c/p via the microprocessor interface block 36 1.3.1 interfacing the framer to the microprocessor over an 8 bit wide bi-directional data bus 37 1.3.2 data access modes. ............................................................................................................................... ............... 37 1.3.2.1 p rogrammed i/o ........................................................................................................................... ..................... 37 1.3.2.2 d ata a ccess using p rogrammed i/o ............................................................................................................... 37 f igure 4. i ntel p i nterface signals during p rogrammed i/o r ead o peration ................................................................... 38 f igure 5. i ntel p i nterface s ignals during p rogrammed i/o w rite o peration ................................................................. 39 f igure 6. m otorola p i nterface signals during a p rogrammed i/o r ead o peration ....................................................... 40 f igure 7. m otorola p i nterface signal during p rogrammed i/o w rite o peration ........................................................... 41 1.3.2.3 b urst m ode i/o for d ata a ccess ................................................................................................................... 41 f igure 8. i ntel p i nterface s ignals , during the i nitial r ead o peration of a b urst c ycle .............................................. 43 f igure 9. i ntel p i nterface s ignals , during subsequent r ead o perations of a b urst i/o c ycle ................................... 44 f igure 10. i ntel p i nterface signals , during the i nitial w rite o peration of a b urst c ycle ........................................... 46 f igure 11. p i nterface s ignals , during subsequent w rite o perations of a b urst i/o c ycle ......................................... 47 f igure 12. m otorola p i nterface s ignals during the i nitial r ead o peration of a b urst c ycle .................................... 48 f igure 13. m otorola p i nterface s ignals , during subsequent r ead o perations of a b urst i/o c ycle ........................ 49 f igure 14. m otorola p i nterface signals , during the i nitial w rite o peration of a b urst c ycle .................................. 51 f igure 15. m otorola p i nterface s ignals during subsequent w rite o perations of a b urst i/o c ycle ........................ 52 1.4 dma read/write operations.................................................................................................. ................. 52 dma-0 write dma interface ...................................................................................................... ............................... 53 f igure 16. dma m ode for the xrt84l38 and a m icroprocessor ......................................................................................... 53 1.5 memory and register map .................................................................................................... .................. 53 1.5.1 memory mapped i/o indirect addressing.................................................................................... .................. 53
xrt84l38 ii octal t1/e1/j1 framer rev. 1.0.1 t able 8: a ddress m ap .............................................................................................................................. .................................. 54 1.6 description of the control registers ....................................................................................... ..... 55 t able 9: pmon t1/e1 r eceive l ine c ode ( bipolar ) v iolation c ounter ............................................................................... 159 t able 10: pmon t1/e1 r eceive l ine c ode ( bipolar ) v iolation c ounter ............................................................................. 159 t able 11: pmon t1/e1 r eceive f raming a lignment b it e rror c ounter ............................................................................ 159 t able 12: pmon t1/e1 r eceive f raming a lignment b it e rror c ounter ............................................................................ 159 t able 13: pmon t1/e1 r eceive s everely e rrored f rame c ounter ................................................................................... 160 t able 14: pmon t1/e1 r eceive crc-4 b lock e rror c ounter - msb ................................................................................. 160 t able 15: pmon t1/e1 r eceive crc-4 b lock e rror c ounter - lsb .................................................................................. 160 t able 16: pmon t1/e1 r eceive f ar -e nd bl ock e rror c ounter - msb .............................................................................. 160 t able 17: pmon t1/e1 r eceive f ar e nd b lock e rror c ounter ......................................................................................... 161 t able 18: pmon t1/e1 r eceive s lip c ounter ....................................................................................................................... 161 t able 19: pmon t1/e1 r eceive l oss of f rame c ounter ..................................................................................................... 161 t able 20: pmon t1/e1 r eceive c hange of f rame a lignment c ounter .............................................................................. 162 t able 21: pmon lapd t1/e1 f rame c heck s equence e rror c ounter .............................................................................. 162 t able 22: t1/e1 prbs b it e rror c ounter msb .................................................................................................................... 162 t able 23: t1/e1 prbs b it e rror c ounter lsb ..................................................................................................................... 163 t able 24: t1/e1 t ransmit s lip c ounter .............................................................................................................................. ... 163 1.7 the interrupt structure within the framer ............................................................................... 16 4 t able 25: l ist of the p ossible c onditions that can g enerate i nterrupts , in each f ramer ............................................. 164 t able 26: a ddress of the b lock i nterrupt s tatus r egisters ............................................................................................ 165 t able 27: b lock i nterrupt s tatus r egister ......................................................................................................................... 166 t able 28: b lock i nterrupt e nable r egister ......................................................................................................................... 167 1.7.1 configuring the interrupt system, at the framer level ...... ............................................................ 167 1.7.1.1 e nabling /d isabling the f ramer for i nterrupt g eneration ....................................................................... 167 t able 29: i nterrupt c ontrol r egister .............................................................................................................................. .... 168 1.7.1.2 c onfiguring the i nterrupt s tatus b its within a given f ramer to be r eset - upon -r ead or w rite - to -c lear . 168 1.7.1.3 a utomatic r eset of i nterrupt e nable b its ................................................................................................. 168 2.0 the e1 framing structure................................................................................................... ...... 170 2.1 the single e1 frame ........................................................................................................ ......................... 170 f igure 17. s ingle e1 f rame d iagram ............................................................................................................................... ....... 170 timeslot 0 ..................................................................................................................... .......................................... 170 timeslot 0 octets within fas frames ............................................................................................ .......................... 170 t able 30: b it f ormat of t imeslot 0 octet within a fas e1 f rame ...................................................................................... 170 bit 0?si (international bit) ................................................................................................... .................................. 171 t able 31: b it f ormat of t imeslot 0 octet within a n on -fas e1 f rame .............................................................................. 171 bit 0?si (international bit) ................................................................................................... .................................. 171 bit 1?fixed at ?1?............................................................................................................. ...................................... 171 bit 2?a (fas frame yellow alarm bit)........................................................................................... ....................... 171 bit 3 through 7?sa4?sa8 (national bits) ........................................................................................ ...................... 171 2.2 the e1 multi-frame structures.............................................................................................. ............ 171 2.2.1 the crc multi-frame structure ... ................................................................................................................. 172 t able 32: b it f ormat of all t imeslot 0 octets within a crc m ulti - frame ......................................................................... 172 2.2.2 cas multi-frames and channel associated signaling . ....................................................................... 172 2.2.2.1 c hannel a ssociated s ignaling ..................................................................................................................... 173 f igure 18. f rame /b yte f ormat of the cas m ulti -f rame s tructure .................................................................................. 173 2.2.2.2 c ommon c hannel s ignaling (ccs) ................................................................................................................ 174 f igure 19. e1 f rame f ormat ............................................................................................................................... .................... 174 3.0 the ds1 framing structure.................................................................................................. .... 175 f igure 20. t1 f rame f ormat ............................................................................................................................... .................... 175 3.1 t1 super frame format (sf) ................................................................................................. ................. 175 f igure 21. t1 s uperframe pcm f ormat ............................................................................................................................... . 176 t able 33: s uperframe f ormat .............................................................................................................................. .................. 176 3.2 t1 extended superframe format .............................................................................................. ........ 177 f igure 22. t1 e xtended s uperframe f ormat ........................................................................................................................ 177 t able 34: e xtended s uperframe f ormat .............................................................................................................................. .177 3.3 slc 96 format (slc)........................................................................................................ ........................... 179 t able 35: slc?96 f s b it c ontents .............................................................................................................................. .......... 179 4.0 the ds1 transmit section ................................................................................................... ....... 180 4.1 the ds1 transmit payload data input interface block .......................................................... 180 4.1.1 description of the transmit payload data input interface block ..... ......................................... 180 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h) ........................ 180 4.1.2 brief discussion of the transmit payload data input interface block operating at 1.544mbit/
xrt84l38 iii rev. 1.0.1 octal t1/e1/j1 framer s mode......................................................................................................................... ............................................... 181 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h)................................................. 181 t able 36: s ignals for different t ransmit timing sources ................................................................................................... 182 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)....................... 182 t able 37: t he t x ts b [3:0] bits when the t ransmit f ractional t1 i nput bit is set to different values ............................ 183 4.1.2.1 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment if t ransmit t iming s ource = t x s er c lk _ n ............................................................................................................................ 18 3 f igure 23. i nterfacing xrt84l38 to local t erminal e quipment with t x s er c lk _ n as t ransmit t iming s ource ............ 184 f igure 24. w aveforms of the signals that connect the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the t ransmit s erial clock being the t iming s ource of the t ransmit s ection ....................... 185 4.1.2.2 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment if the t ransmit t iming s ource = oscclk ...................................................................................................................... ............ 185 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h)................................................. 186 f igure 25. i nterfacing xrt84l38 to the local t erminal e quipment with the oscclk d riven d ivided c lock as t ransmit t im - ing s ource ............................................................................................................................... ................................. 187 f igure 26. w aveforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the oscclk d riven d ivided clock as the timing source of the t ransmit s ection ............... 188 4.1.2.3 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment for l oop - tim - ing applications ............................................................................................................................... ................... 188 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h).................................................. 189 f igure 27. i nterfacing xrt84l38 to local t erminal e quipment with r ecovered r eceive l ine c lock as t ransmit t iming s ource ............................................................................................................................... ....................................... 190 f igure 28. w aveforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the r ecovered r eceive l ine c lock being the timing source of the t ransmit s ection ......... 191 4.1.3 brief discussion of the transmit high-speed back-plane interface .. ......................................... 191 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)....................... 191 t able 38: t ransmit m ultiplex e nable bit and t ransmit i nterface m ode s elect [1:0] bits with the resulting t ransmit b ack - plane i nterface data rates .............................................................................................................................. ...... 192 t ransmit m ultiplex e nable b it = 0 ...................................................................................................... 192 t ransmit m ultiplex e nable b it = 1 ...................................................................................................... 193 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)........................ 193 4.1.3.1 t1 t ransmit i nput i nterface - mvip 2.048 mh z ........................................................................................... 194 t able 39: t he mapping of t1 frame into e1 framing format ................................................................................................ 194 f igure 29. i nterfacing xrt84l38 to the local t erminal e quipment using mvip 2.048m bit / s d ata b us ......................... 195 f igure 30. t iming d iagram of the i nput s ignals to the f ramer when running at mvip 2.048m bit / s m ode ..................... 195 4.1.3.2 t1 t ransmit i nput i nterface - 4.096 mh z ..................................................................................................... 195 t able 40: t he mapping of t1 frame into e1 framing format ................................................................................................ 196 f igure 31. i nterfacing xrt84l38 to the local t erminal e quipment using 4.096m bit / s d ata b us ................................... 197 f igure 32. t iming d iagram of the i nput s ignals to the f ramer when running at 4.096m bit / s m ode ............................... 197 4.1.3.3 t1 t ransmit i nput i nterface - 8.192 mh z ..................................................................................................... 197 t able 41: t he mapping of t1 frame into e1 framing format ................................................................................................ 198 f igure 33. i nterfacing xrt84l38 to the l ocal t erminal e quipment using 8.192m bit / s d ata b us .................................. 199 f igure 34. t iming d iagram of the i nput s ignals to the f ramer when running at 8.192m bit / s m ode ............................... 199 4.1.3.4 t1 t ransmit i nput i nterface - m ultiplexed 12.352m bit / s ........................................................................... 199 f irst o ctet of 12.352m bit / s d ata s tream .......................................................................................... 200 s econd o ctet of 12.352m bit / s d ata s tream ...................................................................................... 200 t hird o ctet of 12.352m bit / s d ata s tream ......................................................................................... 200 s ixth o ctet of 12.352m bit / s d ata s tream ......................................................................................... 201 s eventh o ctet of 12.352m bit / s d ata s tream .................................................................................... 201 e ighth o ctet of 12.352m bit / s d ata s tream ....................................................................................... 201 n ineth o ctet of 12.352m bit / s d ata s tream ....................................................................................... 201 f igure 35. i nterfacing xrt84l38 to the l ocal t erminal e quipment using b it -m ultiplexed 12.352m bit / s d ata b us ..... 202 f igure 36. t iming d iagram of the i nput s ignals to the f ramer when running at 12.352m bit / s m ode ............................. 202 4.1.3.5 t1 t ransmit i nput i nterface - b it -m ultiplexed 16.384m bit / s ..................................................................... 202 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 203 n ineth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 203 t enth o ctet of 16.384m bit / s d ata s tream ........................................................................................ 203 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 204 f ourteenth o ctet of 16.384m bit / s d ata s tream .............................................................................. 204 f ifteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 204 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 204 f igure 37. i nterfacing xrt84l38 to the l ocal t erminal e quipment using 16.384m bit / s d ata b us ................................ 205
xrt84l38 iv octal t1/e1/j1 framer rev. 1.0.1 f igure 38. t iming d iagram of the i nput s ignals to the f ramer when running at b it -m ultiplexed 16.384m bit / s m ode 205 4.1.3.6 t1 t ransmit i nput i nterface - hmvip 16.384m bit / s ..................................................................................... 205 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 206 n inth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 206 e leventh o ctet of 16.384m bit / s d ata s tream ................................................................................... 207 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 207 f ifteenth o ctet of 16.384m bit / s d ata s tream ................................................................................... 207 t enth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 207 t welfth o ctet of 16.384m bit / s d ata s tream ..................................................................................... 207 f ourteenth o ctet of 16.384m bit / s d ata s tream ............................................................................... 207 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 208 f igure 39. i nterfacing xrt84l38 to the l ocal t erminal e quipment using hmvip 16.384m bit / s d ata b us .................... 209 f igure 40. t iming d iagram of the i nput s ignals to the f ramer when running at hmvip 16.384m bit / s m ode ................ 209 4.1.3.7 t1 t ransmit i nput i nterface - h.100 16.384m bit / s ....................................................................................... 209 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 210 n inth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 210 e leventh o ctet of 16.384m bit / s d ata s tream ................................................................................... 211 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 211 f ifteenth o ctet of 16.384m bit / s d ata s tream ................................................................................... 211 t enth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 211 t welfth o ctet of 16.384m bit / s d ata s tream ..................................................................................... 211 f ourteenth o ctet of 16.384m bit / s d ata s tream ............................................................................... 211 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 212 f igure 41. i nterfacing xrt84l38 to the l ocal t erminal e quipment using h.100 16.384m bit / s d ata b us ...................... 213 f igure 42. t iming d iagram of the i nput s ignals to the f ramer when running at h.100 16.384m bit / s m ode .................. 213 5.0 the ds1 receive section .................................................................................................... ......... 214 5.1 the ds1 receive payload data output interface block ......................................................... 214 5.1.1 description of the receive payload data output interface block ............................................. 214 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h)......................... 214 5.1.2 the receive payload data output interface block operating at 1.544mbit/s mode .............. 214 s lip b uffer c ontrol r egister (sbcr) (i ndirect a ddress = 0 xn 0h, 0 x 16h) .................................. 215 s lip b uffer c ontrol r egister (sbcr) (i ndirect a ddress = 0 xn 0h, 0 x 16h) .................................. 215 t able 42: t he r eceive s erial c lock and r eceive s ingle -f rame s ynchronization signals for different s lip b uffer settings 216 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h)......................... 217 t able 43: t he r x ts b [2:0] bits when the r eceive f ractional t1 o utput bit is set to different values .......................... 218 5.1.2.1 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is bypassed ............................................................................................................................... .............. 218 f igure 43. i nterfacing xrt84l38 local t erminal e quipment with s lip b uffer b ypassed and r ecovered r eceive l ine c lock as r eceive t iming s ource ............................................................................................................................... ........ 219 f igure 44. w aveforms of the s ignals c onnecting the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is b ypassed and the r ecovered l ine c lock is the t iming s ource of the r eceive s ection ............................................................................................................................... ...................................... 220 5.1.2.2 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is enabled ............................................................................................................................... ................ 220 s lip b uffer s tatus r egister (sbsr) (i ndirect a ddress = 0 xn ah, 0 x 08h) ..................................... 221 f igure 45. i nterfacing xrt84l38 to local t erminal e quipment with s lip b uffer e nabled or a cts as fifo ................ 222 f igure 46. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t ermi - nal e quipment when the s lip b uffer is e nabled ................................................................................................... 223 5.1.2.3 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is configured as fifo .......................................................................................................................... . 223 fifo l atency r egister (fifolr) (i ndirect a ddress = 0 xn 0h, 0 x 17h) ............................................ 223 f igure 47. i nterfacing xrt84l38 to local t erminal e quipment with s lip b uffer e nabled or a cts as fifo ................ 224 f igure 48. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t ermi - nal e quipment when the s lip b uffer is acted as fifo......................................................................................... 225 5.1.3 high speed receive back-plane interface.................................................................................. .............. 225 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h)......................... 225 t able 44: r eceive m ultiplex e nable bit and r eceive i nterface m ode s elect [1:0] bits with the resulting r eceive b ack - plane i nterface data rates .............................................................................................................................. ................. 226 r eceive m ultiplex e nable b it = 0......................................................................................................... 226 r eceive m ultiplex e nable b it = 1......................................................................................................... 227
xrt84l38 v rev. 1.0.1 octal t1/e1/j1 framer r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h) ........................ 227 5.1.3.1 t1 r eceive i nput i nterface - mvip 2.048 mh z .............................................................................................. 227 t able 45: t he mapping of t1 frame into e1 framing format ................................................................................................ 228 f igure 49. i nterfacing xrt84l38 to local t erminal e quipment using mvip 2.048m bit / s d ata b us ................................ 229 f igure 50. t iming d iagram of i nput signals to the f ramer when running at mvip 2.048m bit / s ...................................... 229 5.1.3.2 t1 r eceive i nput i nterface - 4.096 mh z ....................................................................................................... 229 t able 46: t he mapping of t1 frame into e1 framing format ................................................................................................ 230 f igure 51. i nterfacing xrt84l38 to local t erminal e quipment using 4.096m bit / s d ata b us ......................................... 231 f igure 52. t iming d iagram of i nput signals to the f ramer when running at 4.096m bit / s ................................................ 231 5.1.3.3 t1 r eceive i nput i nterface - 8.192 mh z ....................................................................................................... 231 t able 47: t he mapping of t1 frame into e1 framing format ................................................................................................ 232 f igure 53. i nterfacing xrt84l38 to local t erminal e quipment using 8.192m bit / s d ata b us ......................................... 233 f igure 54. t iming d iagram of i nput signals to the f ramer when running at 8.192m bit / s ................................................ 233 5.1.3.4 t1 r eceive i nput i nterface - m ultiplexed 12.352m bit / s ............................................................................. 233 f irst o ctet of 12.352m bit / s d ata s tream .......................................................................................... 234 s econd o ctet of 12.352m bit / s d ata s tream ...................................................................................... 234 t hird o ctet of 12.352m bit / s d ata s tream ......................................................................................... 234 s ixth o ctet of 12.352m bit / s d ata s tream ......................................................................................... 235 s eventh o ctet of 12.352m bit / s d ata s tream .................................................................................... 235 e ighth o ctet of 12.352m bit / s d ata s tream ....................................................................................... 235 n ineth o ctet of 12.352m bit / s d ata s tream ....................................................................................... 235 f igure 55. i nterfacing xrt84l38 to local t erminal e quipment using 12.352m bit / s d ata b us ....................................... 236 f igure 56. t iming d iagram of i nput signals to the f ramer when running at 12.352m bit / s .............................................. 236 5.1.3.5 t1 r eceive i nput i nterface - b it -m ultiplexed 16.384m bit / s ....................................................................... 236 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 237 n inth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 237 t enth o ctet of 16.384m bit / s d ata s tream ........................................................................................ 237 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 238 f ourteenth o ctet of 16.384m bit / s d ata s tream .............................................................................. 238 f ifteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 238 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 238 f igure 57. i nterfacing xrt84l38 to local t erminal e quipment using 16.384m bit / s d ata b us ....................................... 239 f igure 58. t iming d iagram of i nput signals to the f ramer when running at b it - multiplexed 16.384m bit / s ................... 239 5.1.3.6 t1 r eceive i nput i nterface - hmvip 16.384m bit / s ....................................................................................... 239 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 240 n inth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 240 e leventh o ctet of 16.384m bit / s d ata s tream ................................................................................... 240 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 241 f ifteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 241 t enth o ctet of 16.384m bit / s d ata s tream ........................................................................................ 241 t welfth o ctet of 16.384m bit / s d ata s tream .................................................................................... 241 f ourteenth o ctet of 16.384m bit / s d ata s tream .............................................................................. 241 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 241 f igure 59. i nterfacing xrt84l38 to local t erminal e quipment using 16.384m bit / s d ata b us ....................................... 242 f igure 60. t iming d iagram of i nput signals to the f ramer when running at hmvip 16.384m bit / s .................................. 243 5.1.3.7 t1 r eceive i nput i nterface - h.100 16.384m bit / s ......................................................................................... 243 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 243 n inth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 244 e leventh o ctet of 16.384m bit / s d ata s tream ................................................................................... 244 t hirteenth o ctet of 16.384m bit / s d ata s tream ................................................................................ 244 f ifteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 244 t enth o ctet of 16.384m bit / s d ata s tream ........................................................................................ 245 t welfth o ctet of 16.384m bit / s d ata s tream .................................................................................... 245 f ourteenth o ctet of 16.384m bit / s d ata s tream .............................................................................. 245 s ixteenth o ctet of 16.384m bit / s d ata s tream .................................................................................. 245 f igure 61. i nterfacing xrt84l38 to local t erminal e quipment using h.100 16.384m bit / s d ata b us ............................. 246 f igure 62. t iming d iagram of i nput signals to the f ramer when running at h.100 16.384m bit / s ................................... 246 6.0 the e1 transmit section .................................................................................................... ........ 247 6.1 the e1 transmit payload data input interface block............................................................. 247
xrt84l38 vi octal t1/e1/j1 framer rev. 1.0.1 6.1.1 description of the transmit payload data input interface block ..... ......................................... 247 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h) ........................ 247 6.1.2 brief discussion of the transmit payload data input interface block operating at xrt84v24 compatible 2.048mbit/s mode .................................................................................................... ........................ 248 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h) ................................................. 248 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h) ........................ 249 6.1.2.1 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment if t ransmit t iming s ource = t x s er c lk _ n ............................................................................................................................ 25 0 f igure 63. i nterfacing xrt84l38 to local terminal equipment with t x s er c lk _ n as t ransmit t iming s ource ............. 251 f igure 64. w aveforms of the signals that connect the t ransmit p ayload d ata i nput i nterface b lock to the local t erminal e quipment with the t ransmit s erial clock being the timing source of the t ransmit s ection ........................ 252 6.1.2.2 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment if the t ransmit t iming s ource = oscclk ...................................................................................................................... ............ 252 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h) ................................................. 253 f igure 65. i nterfacing xrt84l38 to local terminal equipment with oscclk driven divided clock as transmit timing source 254 f igure 66. w averforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the oscclk driven divided clock as the timing source of the t ransmit s ection ................. 255 6.1.2.3 c onnect the t ransmit p ayload d ata i nput i nterface block to the l ocal t erminal e quipment for l oop - tim - ing applications ............................................................................................................................... ................... 255 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h) ................................................. 256 f igure 67. i nterfacing xrt84l38 to local terminal equipment with recovered receive line clock as transmit timing source 257 f igure 68. w averforms of the signals connecting the t ransmit p ayload d ata input interface block to the local t erminal e quipment with the r ecovered r eceive l ine c lock being the timing source of transmit section ................. 258 6.1.3 brief discussion of the transmit high-speed back-plane interface .. ......................................... 258 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h) ....................... 258 t ransmit m ultiplex e nable b it = 0....................................................................................................... 259 t ransmit m ultiplex e nable b it = 1....................................................................................................... 260 t ransmit i nterface c ontrol r egister (ticr) ( ndirect a ddress = 0 xn 0h, 0 x 20h) ......................... 260 6.1.3.1 e1 t ransmit i nput i nterface - mvip 2.048 mh z ........................................................................................... 260 f igure 69. i nterfacing xrt84l38 to local terminal equipment using mvip 2.048m bit / s data bus .................................. 261 f igure 70. t iming diagram of input signals to the framer when running at mvip 2.048m bit / s ........................................ 262 6.1.3.2 e1 t ransmit i nput i nterface - 4.096 mh z ..................................................................................................... 262 f igure 71. i nterfacing xrt84l38 to local terminal equipment using 4.096m bit / s data bus ........................................... 263 f igure 72. t iming diagram of input signals to the framer when running at 4.096m bit / s mode ........................................ 263 6.1.3.3 e1 t ransmit i nput i nterface - 8.192 mh z ..................................................................................................... 263 f igure 73. i nterfacing xrt84l38 to local terminal equipment using 8.192m bit / s data bus ........................................... 264 f igure 74. t iming diagram of input signals to the framer when running at 8.192m bit / s mode ........................................ 265 6.1.3.4 e1 t ransmit i nput i nterface - b it -m ultiplexed 16.384m bit / s ..................................................................... 265 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 266 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 266 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 266 s ixth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 266 s eventh o ctet of 16.384m bit / s d ata s tream ..................................................................................... 266 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 267 f igure 75. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus ......................................... 268 f igure 76. iming signal when the framer is running at b it -m ultiplexed 16.384m bit / s mode ............................................ 268 6.1.3.5 e1 t ransmit i nput i nterface - hmvip 16.384m bit / s ..................................................................................... 268 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 269 t hird o ctet of 16.384m bit / s d ata s tream .......................................................................................... 269 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 269 s eventh o ctet of 16.384m bit / s d ata s tream ..................................................................................... 269 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 270 f ourth o ctet of 16.384m bit / s d ata s tream ...................................................................................... 270 s ixth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 270 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 270 f igure 77. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus ......................................... 271 f igure 78. t iming s ignal when the framer is running at hmvip 16.384m bit / s mode ......................................................... 271 6.1.3.6 e1 t ransmit i nput i nterface - h.100 16.384m bit / s ...................................................................................... 271 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 272
xrt84l38 vii rev. 1.0.1 octal t1/e1/j1 framer t hird o ctet of 16.384m bit / s d ata s tream ......................................................................................... 272 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 272 s eventh o ctet of 16.384m bit / s d ata s tream .................................................................................... 273 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 273 f ourth o ctet of 16.384m bit / s d ata s tream ...................................................................................... 273 s ixth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 273 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 273 f igure 79. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus ......................................... 274 f igure 80. t iming signal when the framer is running at h.100 16.384m bit / s mode ........................................................... 275 6.2 the receive payload data output interface block................................................................. 275 6.2.1 description of the receive payload data output interface block............................................. 275 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h) ........................ 276 6.2.2 brief discussion of the receive payload data output interface block operating at xrt84v24 compatible 2.048mbit/s mode .................................................................................................... ........................ 276 s lip b uffer c ontrol r egister (sbcr) (i ndirect a ddress = 0 xn 0h, 0 x 16h) ................................... 276 s lip b uffer c ontrol r egister (sbcr) (i ndirect a ddress = 0 xn 0h, 0 x 16h) ................................... 277 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h) ........................ 278 6.2.2.1 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is bypassed ............................................................................................................................... .............. 279 f igure 81. i nterfacing xrt84l38 to local terminal equipment with slip buffer bypassed and recovered receive line clock as receive timing source ............................................................................................................................... .......... 280 f igure 82. w aveforms of the s ignals c onnecting the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is b ypassed and the r ecovered l ine c lock is the t iming s ource of the r eceive s ection ............................................................................................................................... ...................................... 281 6.2.2.2 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is enabled ............................................................................................................................... ................ 281 s lip b uffer s tatus r egister (sbsr) (i ndirect a ddress = 0 xn ah, 0 x 08h)...................................... 282 f igure 83. i nterfacing xrt84l38 to local terminal equipment with slip buffer enabled or acts as fifo ..................... 283 f igure 84. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t ermi - nal e quipment when the s lip b uffer is e nabled ................................................................................................... 284 6.2.2.3 c onnect the r eceive p ayload d ata o utput i nterface block to the l ocal t erminal e quipment if the s lip b uffer is configured as fifo .......................................................................................................................... . 284 fifo l atency r egister (fifol) (i ndirect a ddress = 0 xn 0h, 0 x 17h) .............................................. 284 f igure 85. i nterfacing xrt84l38 to local terminal equipment with slip buffer enabled or acts as fifo ..................... 285 f igure 86. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t ermi - nal e quipment when the s lip b uffer is acted as fifo......................................................................................... 286 6.2.3 high speed receive back-plane interface.................................................................................. .............. 286 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h) ........................ 286 r eceive m ultiplex e nable b it = 0 ........................................................................................................ 287 r eceive m ultiplex e nable b it = 1 ........................................................................................................ 288 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 22h) ......................... 288 6.2.3.1 e1 r eceive i nput i nterface - mvip 2.048 mh z ............................................................................................. 288 f igure 87. i nterfacing xrt84l38 to local terminal equipment using mvip 2.048m bit / s data bus .................................. 289 f igure 88. t iming d iagram of i nput signals to the f ramer when running at mvip 2.048m bit / s ...................................... 289 6.2.3.2 e1 r eceive i nput i nterface - 4.096 mh z ....................................................................................................... 290 f igure 89. i nterfacing xrt84l38 to local terminal equipment using 4.096m bit / s data bus ........................................... 290 f igure 90. t iming d iagram of input signals to the framer when running at 4.096m bit / s mode ....................................... 291 6.2.3.3 e1 r eceive i nput i nterface - 8.192 mh z ....................................................................................................... 291 f igure 91. i nterfacing xrt84l38 to local terminal equipment using 8.192m bit / s data bus ........................................... 292 f igure 92. t iming diagram of input signals to the framer when running at 8.192m bit / s mode ........................................ 292 6.2.3.4 e1 r eceive i nput i nterface - b it -m ultiplexed 16.384m bit / s ....................................................................... 292 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 293 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 293 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 294 s ixth o ctet of 16.384m bit / s d ata s tream ......................................................................................... 294 s eventh o ctet of 16.384m bit / s d ata s tream .................................................................................... 294 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 294 f igure 93. i nterfacing xrt84l38 to local terminal equipment using 16.384 m bit / s data bus ........................................ 295 f igure 94. t iming signal when the framer is running at b it -m ultiplexed 16.384m bit / s mode .......................................... 295 6.2.3.5 e1 r eceive i nput i nterface - hmvip 16.384m bit / s ....................................................................................... 295 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 296
xrt84l38 viii octal t1/e1/j1 framer rev. 1.0.1 t hird o ctet of 16.384m bit / s d ata s tream .......................................................................................... 296 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 296 s eventh o ctet of 16.384m bit / s d ata s tream ..................................................................................... 296 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 297 f ourth o ctet of 16.384m bit / s d ata s tream ...................................................................................... 297 s ixth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 297 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 297 f igure 95. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus ......................................... 298 f igure 96. t iming s ignal when the framer is running at hmvip 16.384m bit / s mode ......................................................... 298 6.2.3.6 e1 r eceive i nput i nterface - h.100 16.384m bit / s ......................................................................................... 298 f irst o ctet of 16.384m bit / s d ata s tream .......................................................................................... 299 t hird o ctet of 16.384m bit / s d ata s tream .......................................................................................... 299 f ifth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 299 s eventh o ctet of 16.384m bit / s d ata s tream ..................................................................................... 299 s econd o ctet of 16.384m bit / s d ata s tream ...................................................................................... 300 f ourth o ctet of 16.384m bit / s d ata s tream ...................................................................................... 300 s ixth o ctet of 16.384m bit / s d ata s tream .......................................................................................... 300 e ighth o ctet of 16.384m bit / s d ata s tream ....................................................................................... 300 f igure 97. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus ......................................... 301 f igure 98. t iming s ignal when the framer is running at h.100 16.384m bit / s mode ........................................................... 301 7.0 ds1 overhead interface block .............................................................................................. 302 7.1 ds1 transmit overhead input interface block........................................................................... 302 7.1.1 description of the ds1 transmit overhead input interface block ..... ......................................... 302 f igure 99. b lock d iagram of the ds1 t ransmit o verhead i nput i nterface of the xrt84l38 ........................................ 302 7.1.2 configure the ds1 transmit overhead input interface module as source of the facility data link (fdl) bits in esf framing format mode ..................................................................................... .......... 302 t ransmit d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah)........................ 303 t ransmit d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah)........................ 303 f igure 100. ds1 t ransmit o verhead i nput i nterface t iming in esf f raming f ormat mode ............................................. 303 7.1.3 configure the ds1 transmit overhead input interface module as source of the signaling framing (fs) bits in n or slc?96 framing format mode......................................................................... 3 04 t ransmit d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah)........................ 304 f igure 101. ds1 t ransmit o verhead i nput t iming in n or slc?96 f raming f ormat m ode .............................................. 304 7.1.4 configure the ds1 transmit overhead input interface module as source of the remote sig - naling (r) bits in t1dm framing format mode.................................................................................... ........ 304 t ransmit d ata link select register ( tdlsr ) (i ndirect address = 0 xn 0h, 0 x 0ah) ........................... 305 f igure 102. ds1 t ransmit o verhead i nput i nterface module in t1dm f raming f ormat mode ........................................ 305 7.2 ds1 receive overhead output interface block ......................................................................... 306 7.2.1 description of the ds1 receive overhead output interface block ............................................. 306 f igure 103. b lock d iagram of the ds1 r eceive o verhead o utput i nterface of xrt84l38............................................ 306 7.2.2 configure the ds1 receive overhead output interface module as destination of the facility data link (fdl) bits in esf framing format mode ................................................................................ .... 306 r eceive d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah).......................... 307 r eceive d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah).......................... 307 f igure 104. ds1 r eceive o verhead o utput i nterface module in esf framing format mode ........................................... 308 7.2.3 configure the ds1 receive overhead output interface module as destination of the signaling framing (fs) bits in n or slc?96 framing format mode......................................................................... 3 08 r eceive d ata l ink s elect r egister (tdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah)......................... 308 f igure 105. ds1 r eceive o verhead o utput i nterface t iming in n or slc?96 f raming f ormat mode ............................ 309 7.2.4 configure the ds1 receive overhead output interface module as destination of the remote signaling (r) bits in t1dm framing format mode ................................................................................. .... 309 r eceive d ata l ink s elect r egister (rdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) ........................ 309 f igure 106. ds1 r eceive o verhead o utput i nterface t iming in t1dm f raming f ormat mode ......................................... 310 8.0 e1 overhead interface block ................................................................................................ . 311 8.1 e1 transmit overhead input interface block ............................................................................. 311 8.1.1 description of the e1 transmit overhead input interface block. ................................................ 311 f igure 107. b lock d iagram of the e1 t ransmit o verhead i nput i nterface of xrt84l38 ................................................ 311 8.1.2 configure the e1 transmit overhead input interface module as source of the national bit se - quence in e1 framing format mode............................................................................................... ................ 311 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) .................................. 312 t ransmit s ignaling and d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) 312
xrt84l38 ix rev. 1.0.1 octal t1/e1/j1 framer f igure 108. e1 t ransmit o verhead i nput i nterface t iming ................................................................................................. 313 8.2 e1 receive overhead interface .............................................................................................. ........... 313 8.2.1 description of the e1 receive overhead output interface block ............................................... 313 f igure 109. b lock d iagram of the e1 r eceive o verhead o utput i nterface of xrt84l38 .............................................. 314 8.2.2 configure the e1 receive overhead output interface module as source of the national bit sequence in e1 framing format mode............................................................................................. ............. 314 r eceive s ignaling and d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) 314 f igure 110. e1 r eceive o verhead o utput i nterface t iming ................................................................................................ 315 9.0 ds1 transmit framer block.................................................................................................. ... 316 9.1 how to configure xrt84l38 to operate in ds1 mode ................................................................. 316 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h)................................................. 316 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 316 9.2 how to configure the framer to transmit data in various ds1 framing formats .... 317 f raming s elect r egister (fsr) (in direct a ddress = 0 xn 0h, 0 x 07h) .............................................. 317 9.2.1 how to configure the framer to input framing alignment bits from different sources 317 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) ................................... 318 9.2.2 how to configure the framer to input crc-6 bits from different sources .. .......................... 318 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) ................................... 319 9.3 how to configure the framer to apply data and signaling conditioning to ds1 payload data on a per-channel basis.................................................................................................... ........ 319 t ransmit c hannel c ontrol r egister (tccr) (i ndirect a ddress = 0 xn 2h, 0 x 00h - 0 x 1fh) .......... 320 9.3.1 how to apply user idle code to the ds1 payload data ...................................................................... 320 u ser idle c ode r egister (ucr) (i ndirect a ddress = 0 xn 02h, 0 x 20h - 0 x 37h) ............................ 321 9.4 how to configure the xrt84l38 framer to apply zero code suppression to ds1 payload data on a per-channel basis.................................................................................................... ........ 321 t ransmit c hannel c ontrol r egister (tccr) (i ndirect a ddress = 0 xn 2h, 0 x 00h - 0 x 1fh) ......... 321 9.5 how to configure the xrt84l38 framer to transmit robbed-bit signaling information 321 9.5.1 brief discussion of robbed-bit signaling in ds1 framing format ................................................. 322 9.5.2 configure the framer to transmit robbed-bit signaling. ................................................................ 323 9.5.2.1 i nsert s ignaling b its from tscr r egister ................................................................................................. 323 t ransmit s ignaling c ontrol r egister (tscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 57h) ........ 324 9.5.2.2 i nsert s ignaling b its from t x s ig _ n p in ....................................................................................................... 324 f igure 111. t iming d iagram of the t x s ig _ n i nput ................................................................................................................. 324 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)........................ 325 9.5.2.3 i nsert s ignaling d ata from t x s er _ n p in ..................................................................................................... 325 9.5.2.4 e nable r obbed - bit s ignaling and s ignaling d ata s ource c ontrol ........................................................ 325 t ransmit s ignaling c ontrol r egister (tscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 57h) ........ 325 t ransmit s ignaling c ontrol r egister (tscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 57h) ........ 326 9.6 how to configure the xrt84l38 framer to generate and transmit alarms and error in - dications to remote terminal ................................................................................................... ...... 326 9.6.1 brief discussion of alarms and error conditions ... ........................................................................... 326 f igure 112. s imple d iagram of ds1 s ystem m odel .............................................................................................................. 327 f igure 113. g eneration of y ellow a larm by the cpe upon detection of line failure ..................................................... 328 f igure 114. g eneration of ais by the r epeater upon detection of y ellow a larm originated by the cpe................... 329 f igure 115. g eneration of y ellow a larm by the cpe upon detection of ais originated by the r epeater ................... 330 9.6.2 how to configure the framer to transmit ais ... ................................................................................... 330 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h).......................................... 331 9.6.3 how to configure the framer to generate red alarm ..................................................................... 33 1 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h).......................................... 331 9.6.4 how to configure the framer to transmit yellow alarm ... ............................................................ 331 9.6.4.1 t ransmit y ellow a larm in sf m ode ............................................................................................................. 331 9.6.4.2 t ransmit y ellow a larm in esf m ode ........................................................................................................... 332 9.6.4.3 t ransmit y ellow a larm in n m ode ............................................................................................................... 332 9.6.4.4 t ransmit y ellow a larm in t1dm m ode ........................................................................................................ 332 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h).......................................... 333 10.0 ds1 receive framer block.................................................................................................. .... 334 10.1 how to configure xrt84l38 to operate in ds1 mode ............................................................... 334 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h)................................................. 334 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 334 10.2 how to configure the framer to receive data in various ds1 framing formats ..... 335
xrt84l38 x octal t1/e1/j1 framer rev. 1.0.1 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h) ............................................... 335 10.3 how to configure the framer to apply dat a and signaling conditioning to received ds1 payload data on a per-channel basis ......................................................................................... 33 6 r eceive c hannel c ontrol r egister (rccr) (i ndirect a ddress = 0 xn 2h, 0 x 60h - 0 x 7fh) ............ 337 r eceive u ser idle c ode r egister (ucr) (i ndirect a ddress = 0 xn 02h, 0 x 80h - 0 x 97h)................ 337 10.4 how to configure the xrt84l38 framer to apply zero code suppression to received ds1 payload data on a per-channel basis ......................................................................................... 33 7 r eceive c hannel c ontrol r egister (rccr) (i ndirect a ddress = 0 xn 2h, 0 x 60h - 0 x 7fh) ............ 338 10.5 how to configure the xrt84l38 framer to extract robbed-bit signaling information 338 10.5.1 configure the framer to receive and extract robbed-bit signaling.. ..................................... 338 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x b7h) ......... 339 f ramer i nterrupt e nable r egister (fier) (i ndirect a ddress = 0 xn ah, 0 x 05h) ............................ 339 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h) ............................... 339 f ramer i nterrupt s tatus r egister (fisr) (i ndirect a ddress = 0 xn ah, 0 x 04h) ............................ 340 s ignaling c hange r egisters (scr) (i ndirect a ddress = 0 xn 0h, 0 x 0dh - 0 x 0fh).......................... 340 10.5.1.1 s tore s ignaling b its into rsra r egister a rray ..................................................................................... 340 r eceive s ignaling r egister a rray (rsra) (i ndirect a ddress = 0 xn 4h, 0 x 00h - 0 x 17h) .............. 341 10.5.1.2 o utputting s ignaling b its through r x s ig _ n p in ...................................................................................... 341 r eceive i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h) ......................... 341 f igure 116. t iming d iagram of the r x s ig _ n o utput pin ....................................................................................................... 342 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x b7h) ......... 342 10.5.1.3 s end s ignaling d ata through r x s er _ n p in ............................................................................................... 342 10.5.1.4 s ignaling d ata s ubstitution ....................................................................................................................... 342 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x b7h) ......... 342 r eceive s ubstitution s ignaling r egister (rssr) (i ndirect a ddress = 0 xn 02h, 0 x 80h - 0 x 97h) . 343 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 57h) .......... 344 10.6 how to configure the framer to detect alarms and error conditions...................... 344 10.6.1 how to configure the framer to detect ais alarm......................................................................... .. 344 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h) ......................................... 345 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 345 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) .............................. 345 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 346 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 346 10.6.2 how to configure the framer to detect red alarm ......................................................................... 346 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 347 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 347 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 347 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 348 10.6.3 how to configure the framer to detect yellow alarm ................................................................. 348 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h).......... 348 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 348 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 349 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 349 10.6.4 how to configure the framer to detect bipolar violation .......................................................... 349 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 350 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 350 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 350 10.6.5 how to configure the framer to detect loss of signal ................................................................ 350 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h).......... 351 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 351 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 351 11.0 e1 transmit framer block.................................................................................................. .... 352 11.1 how to configure xrt84l38 to operate in e1 mode.................................................................. 352 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h) .................................................. 352 11.2 how to configure the framer to transmit and receive data in e1 framing format 352 11.2.1 how to configure the framer to choose fas searching algorithm ......................................... 352 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h) .............................................. 353
xrt84l38 xi rev. 1.0.1 octal t1/e1/j1 framer 11.2.2 how to configure the framer to enable crc-4 multi-frame alignment and select the locking criteria ....................................................................................................................... .............................................. 353 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 353 11.2.3 how to configure the framer to enable cas multi-frame alignment ...................................... 353 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 354 11.2.4 how to configure the framer to input the framing alignment bits from different sources 354 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) ................................... 354 11.2.5 how to configure the framer to input crc-4 bits from different sources .......................... 355 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) .................................. 355 11.2.6 how to configure the framer to input e bits from different sources .. ................................. 355 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) .................................. 356 11.3 how to configure the framer to apply data and signaling conditioning to e1 payload data on a per-channel basis.................................................................................................... ........ 356 t ransmit c hannel c ontrol r egister (tccr) (i ndirect a ddress = 0 xn 2h, 0 x 00h - 0 x 1fh) .......... 357 u ser idle c ode r egister (ucr) (i ndirect a ddress = 0 xn 02h, 0 x 20h - 0 x 3fh) ............................. 358 11.4 how to configure the xrt84l38 framer to transmit signaling information .............. 358 11.4.1 brief discussion of common channel signaling in e1 framing format ..................................... 358 11.4.2 brief discussion of channel associated signaling in e1 framing format .... .......................... 358 11.4.3 configure the framer to transmit channel associated signaling ........................................... 359 11.4.3.1 i nsert s ignaling b its from tscr r egister ............................................................................................... 360 t ransmit s ignaling c ontrol r egister (tscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 5fh)........ 360 11.4.3.2 i nsert s ignaling b its from t x s ig _ n p in ..................................................................................................... 360 f igure 117. t iming d iagram of the t x s ig _ n i nput ................................................................................................................. 361 t ransmit i nterface c ontrol r egister (ticr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)....................... 361 11.4.3.3 i nsert s ignaling b its from t x oh_ n p in ..................................................................................................... 361 f igure 118. t iming d iagram of the t x oh_ n i nput ................................................................................................................. 362 11.4.3.4 i nsert s ignaling d ata from t x s er _ n p in ................................................................................................... 362 11.4.3.5 e nable c hannel a ssociated s ignaling and s ignaling d ata s ource c ontrol ...................................... 362 t ransmit s ignaling c ontrol r egister (tscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 57h) ........ 362 11.5 how to configure the xrt84l38 framer to generate and transmit alarms and error in - dications to remote terminal ................................................................................................... ...... 363 11.5.1 brief discussion of alarms and error conditions . ........................................................................... 363 f igure 119. s imple d iagram of e1 system model .................................................................................................................. 363 f igure 120. g eneration of y ellow a larm by the r epeater upon detection of line failure ............................................ 364 f igure 121. g eneration of ais by the r epeater upon detection of line failure .............................................................. 365 f igure 122. g eneration of y ellow a larm by the cpe upon detection of ais originated by the r epeater ................... 366 f igure 123. g eneration of cas m ulti - frame y ellow a larm and ais16 by the r epeater ................................................. 367 f igure 124. g eneration of cas m ulti - fram y ellow a larm by the cpe upon detection of ?ais16? pattern sent by the r e - peater ............................................................................................................................... ........................................ 368 11.5.2 how to configure the framer to transmit ais . ................................................................................... 368 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h)......................................... 369 11.5.3 how to configure the framer to generate red alarm ................................................................... 369 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h)......................................... 369 11.5.4 how to configure the framer to transmit yellow alarm . ............................................................ 369 11.5.4.1 t ransmit y ellow a larm ............................................................................................................................... 370 11.5.4.2 t ransmit cas m ulti - frame y ellow a larm ................................................................................................ 370 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h)......................................... 371 12.0 e1 receive framer block ................................................................................................... ..... 372 12.1 how to configure xrt84l38 to operate in e1 mode.................................................................. 372 c lock s elect r egister (csr) (i ndirect a ddress = 0 xn 0h, 0 x 00h)................................................. 372 12.2 how to configure the framer to receive data in various e1 framing formats ........ 372 12.2.1 how to configure the framer to choose fas searching algorithm ......................................... 372 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 373 12.2.2 how to configure the framer to enable crc-4 multi-frame alignment and select the locking criteria ....................................................................................................................... .............................................. 373 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 373 12.2.3 how to configure the framer to enable cas multi-frame alignment ...................................... 373 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 374 12.3 how to configure the framer to apply data and signaling conditioning to received e1 payload data on a per-channel basis ......................................................................................... 37 4 r eceive c hannel c ontrol r egister (rccr) (i ndirect a ddress = 0 xn 2h, 0 x 60h - 0 x 7fh) ........... 375
xrt84l38 xii octal t1/e1/j1 framer rev. 1.0.1 r eceive u ser idle c ode r egister (ucr) (i ndirect a ddress = 0 xn 02h, 0 x 80h - 0 x 97h)............... 376 12.4 how to configure the xrt84l38 framer to extract robbed-bit signaling information 376 12.4.1 configure the framer to receive and extract robbed-bit signaling.. ..................................... 376 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x b7h) ......... 376 f ramer i nterrupt e nable r egister (fier) (i ndirect a ddress = 0 xn ah, 0 x 05h) ............................. 377 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h) .............................. 377 f ramer i nterrupt s tatus r egister (fisr) (i ndirect a ddress = 0 xn ah, 0 x 04h) ............................ 377 s ignaling c hange r egisters (scr) (i ndirect a ddress = 0 xn 0h, 0 x 0dh - 0 x 10h).......................... 378 12.4.1.1 s tore s ignaling b its into rsra r egister a rray ..................................................................................... 378 r eceive s ignaling r egister a rray (rsra) (i ndirect a ddress = 0 xn 4h, 0 x 00h - 0 x 1fh) .............. 378 12.4.1.2 o utputting s ignaling b its through r x s ig _ n p in ...................................................................................... 378 r eceive i nterface c ontrol r egister (ricr) (i ndirect a ddress = 0 xn 0h, 0 x 20h)......................... 379 f igure 125. t iming diagram of r x s ig _ n o utput pin .............................................................................................................. 379 12.4.1.3 o utputting s ignaling b its from r x oh_ n p in ............................................................................................ 379 f igure 126. t iming diagram of the r x oh_ n o utput pin ........................................................................................................ 379 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x bfh) .......... 380 12.4.1.4 s end s ignaling d ata through r x s er _ n p in ............................................................................................... 380 12.4.1.5 s ignaling d ata s ubstitution ....................................................................................................................... 380 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x a0h - 0 x bfh) ......... 380 r eceive s ubstitution s ignaling r egister (rssr) (i ndirect a ddress = 0 xn 02h, 0 x 80h - 0 x 9fh) . 380 r eceive s ignaling c ontrol r egister (rscr) (i ndirect a ddress = 0 xn 2h, 0 x 40h - 0 x 5fh).......... 381 12.5 how to configure the framer to detect alarms and error conditions...................... 381 12.5.1 how to configure the framer to detect ais alarm......................................................................... .. 381 a larm g eneration r egister (agr) (i ndirect a ddress = 0 xn 0h, 0 x 08h) ......................................... 383 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 383 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) .............................. 383 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 384 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 384 12.5.2 how to configure the framer to detect red alarm ......................................................................... 384 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 385 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) .............................. 385 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 385 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 386 12.5.3 how to configure the framer to detect yellow alarm ................................................................. 386 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h).......... 386 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) .............................. 386 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 387 12.5.4 how to configure the framer to detect cas multi-frame yellow alarm............................... 387 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 387 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) .............................. 388 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ........................... 388 12.5.5 how to configure the framer to detect bipolar violation .......................................................... 388 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h)......... 389 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 389 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 389 12.5.6 how to configure the framer to detect loss of signal ................................................................ 389 a larm and e rror i nterrupt e nable r egister (aeier) (i ndirect a ddress = 0 xn ah, 0 x 03h).......... 390 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 01h) ............................... 390 a larm and e rror s tatus r egister (aesr) (i ndirect a ddress = 0 xn ah, 0 x 02h) ............................ 390 13.0 ds1 hdlc controller block ................................................................................................. . 390 13.1 ds1 transmit hdlc controller block ........................................................................................ .. 390 13.1.1 description of the ds1 transmit hdlc controller block .............................................................. 390 t ransmit d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) .................... 391 d ata l ink c ontrol r egister (dlcr) i ndirect a ddress = 0 xn 0h, 0 x 13h)......................................... 392 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ....................................... 392 13.1.2 how to configure xrt84l38 to transmit data link information through d or e channels 392 t ransmit c hannel c ontrol r egister (tccr) (i ndirect a ddress = 0 xn 2h, 0 x 00h - 0 x 1fh)........... 392
xrt84l38 xiii rev. 1.0.1 octal t1/e1/j1 framer t ransmit d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah).................... 393 13.1.3 transmit bos (bit oriented signaling) processor... ........................................................................... 393 13.1.3.1 d escription of bos........................................................................................................................... ........... 393 13.1.3.2 h ow to configure the bos p rocessor b lock to transmit bos ............................................................ 393 t ransmit d ata l ink b yte c ount r egister (tdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 14h) ............ 394 t ransmit d ata l ink b yte c ount r egister (tdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 14h) ............ 394 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ....................................... 395 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 395 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ....................................... 395 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h)....................... 396 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h).............................. 396 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 396 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 397 13.1.4 transmit mos (message oriented signaling) or lapd controller . ............................................. 397 f igure 127. lapd c ontroller ............................................................................................................................... ................. 397 13.1.4.1 d iscussion of mos ........................................................................................................................... ............ 398 f igure 128. lapd f rame s tructure ............................................................................................................................... ....... 398 13.1.4.2 h ow to configure the t ransmit hdlc c ontroller b lock to transmit mos........................................ 401 t ransmit d ata l ink b yte c ount r egister (tdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 14h) ............. 401 t ransmit d ata l ink b yte c ount r egister (tdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 14h) ............ 402 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ....................................... 402 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ....................................... 402 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 403 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 403 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h)...................... 403 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h).............................. 404 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 404 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 404 13.1.5 transmit slca96 data link controller . .................................................................................................. 405 f raming s elect r egister (fsr) (i ndirect a ddress = 0 xn 0h, 0 x 07h).............................................. 405 t ransmit slc?96 m essage r egisters ................................................................................................ 406 13.1.5.1 h ow to configure the slc?96 d ata l ink c ontroller to transmit slc?96 d ata l ink m essages ..... 406 t ransmit d ata l ink b yte c ount r egister (tdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 14h) ............ 406 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h)....................... 407 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h)............................... 407 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 408 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 408 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 408 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 408 13.2 ds1 receive hdlc controller block ......................................................................................... .... 409 13.2.1 description of the ds1 receive hdlc controller block................................................................. 40 9 r eceive d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) ..................... 409 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h)...................................... 410 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 410 13.2.2 how to configure xrt84l38 to receive data link information through d or e channels 410 r eceive c hannel c ontrol r egister (rccr) (i ndirect a ddress = 0 xn 2h, 0 x 60h - 0 x 7fh) ........... 410 r eceive d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) ..................... 411 13.2.3 receive bos (bit oriented signaling) processor.......................................................................... ....... 411 13.2.3.1 h ow to configure the bos p rocessor b lock to receive bos .............................................................. 411 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h)...................... 411 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h).............................. 412 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 412 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h)...................... 412 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ........................................ 413 r eceive d ata l ink b yte c ount r egister (rdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 15h)............... 413 r eceive d ata l ink b yte c ount r egister (rdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 15h).............. 414 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 414 13.2.4 receive lapd controller ................................................................................................. ............................. 414
xrt84l38 xiv octal t1/e1/j1 framer rev. 1.0.1 13.2.4.1 h ow to configure the r eceive hdlc c ontroller b lock to receive mos message ............................. 415 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h) ...................... 415 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h) .............................. 416 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 416 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h) ...................... 416 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 417 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h) ...................... 417 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 417 r eceive d ata l ink b yte c ount r egister (rdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 15h) .............. 418 r eceive d ata l ink b yte c ount r egister (rdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 15h) .............. 418 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 418 13.2.5 receive slca96 data link controller ..................................................................................... ................. 419 r eceive slc?96 m essage r egisters .................................................................................................. 419 13.2.5.1 h ow to configure the slc?96 d ata l ink c ontroller to receive slc?96 d ata l ink m essages ....... 419 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h) ...................... 420 b lock i nterrupt e nable r egister (bier) (i ndirect a ddress = 0 xn ah, 0 x 00h) .............................. 420 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) .......................................... 420 d ata l ink i nterrupt e nable r egister (dlier) (i ndirect a ddress = 0 xn ah, 0 x 07h) ...................... 421 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 421 r eceive d ata l ink b yte c ount r egister (rdlbcr) (i ndirect a ddress = 0 xn 0h, 0 x 15h) .............. 421 14.0 e1 hdlc controller block.................................................................................................. ... 423 14.1 e1 transmit hdlc controller block ......................................................................................... .... 423 14.1.1 description of the e1 transmit hdlc controller block ................................................................ 423 s ynchronization mux r egister (smr) (i ndirect a ddress = 0 xn 0h, 0 x 09h) .................................. 423 d ata l ink c ontrol r egister (dlcr) (i ndirect a ddress = 0 xn 0h, 0 x 13h) ...................................... 424 14.1.2 how to configure xrt84l38 to transmit data link information through the national bits (sa4 through sa8)................................................................................................................... ........................................ 424 t ransmit s ignaling and d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) 424 t ransmit s ignaling and d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) 425 14.1.3 how to configure xrt84l38 to transmit data link information through timeslot 16 octet 425 t ransmit s ignaling and d ata l ink s elect r egister (tsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ah) 425 14.1.4 how to configure xrt84l38 to transmit data link information through d or e channels 425 t ransmit c hannel c ontrol r egister (tccr) (i ndirect a ddress = 0 xn 2h, 0 x 00h - 0 x 1fh).......... 426 14.1.5 transmit bos (bit oriented signaling) processor ... ........................................................................... 426 14.1.6 transmit mos (message oriented signaling) or lapd controller ..... ......................................... 426 14.2 e1 receive hdlc controller block.......................................................................................... ...... 426 14.2.1 description of the e1 receive hdlc controller block ................................................................... 4 26 d ata l ink s tatus r egister (dlsr) (i ndirect a ddress = 0 xn ah, 0 x 06h) ......................................... 427 14.2.2 how to configure xrt84l38 to receive data link information through the national bits (sa4 through sa8)................................................................................................................... ........................................ 427 r eceive s ignaling and d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) 428 r eceive s ignaling and d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) 428 14.2.3 how to configure xrt84l38 to receive data link information through timeslot 16 octet 428 r eceive s ignaling and d ata l ink s elect r egister (rsdlsr) (i ndirect a ddress = 0 xn 0h, 0 x 0ch) 429 14.2.4 how to configure xrt84l38 to receive data link information through d or e channels 429 r eceive c hannel c ontrol r egister (rccr) (i ndirect a ddress = 0 xn 2h, 0 x 60h - 0 x 7fh) ........... 429 14.2.5 receive bos (bit oriented signaling) processor.......................................................................... ....... 429 14.2.6 receive lapd controller ................................................................................................. ............................. 429 15.0 transmit liu interface .... ................................................................................................ ......... 431 16.0 receive liu interface..................................................................................................... ........... 431 ordering information........................................................................................................... ..... 432 p ackage d imensions .............................................................................................................................. 432 r evisions ............................................................................................................................... ................. 433
xrt84l38 5 rev. 1.0.1 octal t1/e1/j1 framer t able 1: l ist by p in n umber p in p in n ame p in p in n ame p in p in n ame p in p in n ame a1 tck b1 tdi c1 rxneg_0 d1 rxlineclk_0 a2 rxtsb0_0 rxsig_0 b2 rxserclk_0 c2 tms d2 rxlos_0 a3 rxsync_0 b3 rxmsync_0 rxcrcmsync_0 c3 trst d3 tdo a4 rxcasmsync_0 b4 rxtsb2_0 rxtschn_0 c4 rxtsclk_0 d4 rxser_0 a5 txohclk_0 b5 rxtsb3_0 rx8khz_0 c5 rxohclk_0 d5 rxtsb1_0 rxfrtd_0 a6 nc b6 txser_0 c6 txmsync_0 txinclk_0 d6 txsync_0 a7 txoh_0 b7 nc c7 rxoh_0 d7 rxtsb4_0 a8 txtsb2_0 tx12.352mhz_0 b8 txtsb3_0 txohsync_0 c8 txtsb0_0 txsig_0 d8 txserclk_0 a9 rxser_1 b9 rxserclk_1 c9 rxmsync_1 rxcrcmsync_1 d9 txtsb1_0 txfrtd_0 a10 rxtsb1_1 rxfrtd_1 b10 rxoh_1 c10 txtsb4_0 d10 txtsclk_0 a11 rxcasmsync_1 b11 rxsync_1 c11 rxtsb2_1 rxtschn_1 d11 rxtsclk_1 a12 txsync_1 b12 rxohclk_1 c12 nc d12 rxtsb0_1 rxsig_1 a13 rxtsb4_1 b13 txmsync_1 txinclk_1 c13 nc d13 rxtsb3_1 rx8khz_1 a14 txser_1 b14 txtsclk_1 c14 txoh_1 d14 nc a15 txtsb2_1 tx12.352mhz_1 b15 txtsb1_1 txfrtd_1 c15 txohclk_1 d15 txtsb0_1 txsig_1 a16 txserclk_1 b16 rxsync_2 c16 nc d16 txtsb3_1 txohsync_1 a17 rxserclk_2 b17 nc c17 txtsb4_1 d17 nc a18 rxtsb0_2 rxsig_2 b18 rxcasmsync_2 c18 rxser_2 d18 rxtsclk_2 a19 rxmsync_2 rxcrcmsync_2 b19 rxtsb1_2 rxfrtd_2 c19 rxoh_2 d19 rxohclk_2 a20 nc b20 rxtsb2_2 rxtschn_2 c20 rxtsb3_2 rx8khz_2 d20 txserclk_2 a21 txsync_2 b21 rxtsb4_2 c21 txtsclk_2 d21 txohclk_2 a22 txmsync_2 txinclk_2 b22 txser_2 c22 txtsb1_2 txfrtd_2 d22 txtsb4_2 a23 txtsb0_2 txsig_2 b23 txtsb2_2 tx12.352mhz_2 c23 nc d23 txoh_2 a24 txtsb3_2 txohsync_2 b24 rxser_3 c24 rxsync_3 d24 rxcasmsync_3
xrt84l38 6 octal t1/e1/j1 framer rev. 1.0.1 a25 rxtsclk_3 b25 rxohclk_3 c25 rxtsb0_3 rxsig_3 d25 txtsclk_3 a26 rxmsync_3 rxcrcmsync_3 b26 rxoh_3 c26 rxtsb1_3 rxfrtd_3 d26 rxtsb3_3 rx8khz_3 p in p in n ame p in p in n ame p in p in n ame p in p in n ame e1 nc f1 rxneg_1 g1 rxlineclk_1 h1 rxpos_2 e2 nc f2 txlineclk_0 g2 txlineclk_1 h2 txneg_1 txmx_1 e3 txpos_0 txnrz_0 f3 txneg_0 txmx_0 g3 rxpos_1 h3 txpos_1 txnrz_1 e4 rxpos_0 f4 nc g4 los_0 h4 rxlos_1 e23 rxserclk_3 f23 txoh_3 g23 txserclk_3 h23 txtsb1_3 txfrtd_3 e24 rxtsb2_3 rxtschn_3 f24 txohclk_3 g24 txtsb0_3 txsig_3 h24 txtsb3_3 txohsync_3 e25 txsync_3 f25 txser_3 g25 cs h25 nc e26 rxtsb4_3 f26 txmsync_3 txinclk_3 g26 wr h26 nc p in p in n ame p in p in n ame p in p in n ame p in p in n ame j1 rxlos_2 k1 los_2 l1 txpos_3 txnrz_3 m1 gpo3 cs 0 j2 txlineclk_2 k2 txneg_2 txmx_2 l2 rxpos_3 m2 los_3 j3 rxneg_2 k3 txpos_2 txnrz_2 l3 rxneg_3 m3 txneg_3 txmx_3 j4 los_1 k4 rxlineclk_2 l4 rxlos_3 m4 rxlineclk_3 l11 vdd m11 vdd l12 vdd m12 vdd l13 vdd m13 vss l14 vdd m14 vss l15 vdd m15 vdd l16 vdd m16 vdd j23 txtsb2_3 tx12.352mhz_3 k23 a6 l23 a4 m23 nc j24 data7 k24 data6 l24 data4 m24 int j25 txtsb4_3 k25 data5 l25 blast m25 ptype2 t able 1: l ist by p in n umber p in p in n ame p in p in n ame p in p in n ame p in p in n ame
xrt84l38 7 rev. 1.0.1 octal t1/e1/j1 framer j26 a5 k26 nc l26 a3 m26 a2 p in p in n ame p in p in n ame p in p in n ame p in p in n ame n1 gpo0 sdo0 p1 gpo7 cs1 r1 gpo4 sdo1 t1 oscclk n2 gpo2 sclk0 p2 gpo6 sclk1 r2 rxpos_4 t2 rxneg_4 n3 gpo1 sdi0 p3 test mode r3 reset t3 rxlineclk_4 n4 txlineclk_3 p4 gpo5 sdi1 r4 lop t4 txpos_4 txnrz_4 n11 vdd r11 vdd t11 vss n12 vdd r12 vdd t12 vss n13 vss p13 vss r13 vss t13 vss n14 vss p14 vss r14 vss t14 vss n15 vdd r15 vdd t15 vss n16 vdd r16 vdd t16 vss n23 a1 p23 rdy_ dtack r23 pclk t23 ack1 n24 ale_as p24 ptype1 r24 data0 t24 indirect n25 data3 p25 dben r25 data1 t25 ptype0 n26 data2 p26 a0 r26 rd t26 req0 p in p in n ame p in p in n ame p in p in n ame p in p in n ame u1 rxlos_4 v1 txneg_4 txmx_4 w1 rxneg_5 y1 rxlos_5 u2 8khzref v2 los_4 w2 rxpos_5 y2 txneg_5 txmx_5 u3 nc v3 nc w3 txpos_5 txnrz_5 y3 txlineclk_5 u4 nc v4 txlineclk_4 w4 rxlineclk_5 y4 nc u23 req1 v23 rxohclk_4 w23 rxtsb3_4 rx8khz_4 y23 txserclk_4 u24 rxserclk_4 v24 rxtsclk_4 w24 rxtsb0_4 rxsig_4 y24 rxcasmsync_4 p in p in n ame p in p in n ame p in p in n ame p in p in n ame
xrt84l38 8 octal t1/e1/j1 framer rev. 1.0.1 u25 nc v25 rxmsync_4 rxcrcmsync_4 w25 rxoh_4 y25 rxtsb2_4 rxtschn_4 u26 ack0 v26 rxsync_4 w26 rxser_4 y26 rxtsb1_4 rxfrtd_4 p in p in n ame p in p in n ame p in p in n ame p in p in n ame aa1 los_5 ab1 rxneg_6 ac1 txneg_6 txmx_6 ad1 rxneg_7 aa2 rxpos_6 ab2 txpos_6 txnrz_6 ac2 rxpos_7 ad2 txpos_7 txnrz_7 aa3 rxlos_6 ab3 los_6 ac3 txlineclk_6 aa4 rxlineclk_6 ab4 rxlos_7 ac4 txlineclk_7 ac5 txtsclk_7 ad5 txoh_7 ac6 txserclk_7 ad6 txtsb1_7 txfrtd_7 ac7 txtsb0_7 txsig_7 ad7 rxserclk_7 ac8 rxmsync_7 rxcrcmsync_7 ad8 rxser_7 ac9 rxtsclk_7 ad9 txserclk_6 ac10 rxcasmsync_7 ad10 rxohclk_7 ac11 rxoh_7 ad11 txtsb4_6 ac12 txtsb3_6 txohsync_6 ad12 rxcasmsync_6 ac13 txtsb0_6 txsig_6 ad13 txohclk_6 ac14 txoh_6 ad14 rxsync_6 ac15 rxtsb4_6 ad15 rxserclk_6 ac16 rxtsb0_6 rxsig_6 ad16 rxtsb2_6 rxtschn_6 ac17 txoh_5 ad17 rxohclk_6 ac18 txserclk_5 ad18 txtsb3_5 txohsync_5 ac19 txsync_5 ad19 txser_5 ac20 rxoh_5 ad20 txohclk_5 p in p in n ame p in p in n ame p in p in n ame p in p in n ame
xrt84l38 9 rev. 1.0.1 octal t1/e1/j1 framer ac21 rxtsb1_5 rxfrtd_5 ad21 rxtsb4_5 ac22 rxsync_5 ad22 rxtsb0_5 rxsig_5 aa23 txsync_4 ac23 nc ad23 rxcasmsync_5 aa24 txoh_4 ab24 txtsb0_4 txsig_4 ac24 txtsb1_4 txfrtd_4 ad24 rxmsync_5 rxcrcmsync_5 aa25 nc ab25 txtsclk_4 ac25 txohclk_4 ad25 rxtsclk_5 aa26 rxtsb4_4 ab26 txser_4 ac26 txmsync_4 txinclk_4 ad26 nc p in p in n ame p in p in n ame ae1 txneg_7 txmx_7 af1 los_7 ae2 rxlineclk_7 af2 nc ae3 nc af3 txohclk_7 ae4 txtsb4_7 af4 txtsb3_7 txohsync_7 ae5 txtsb2_7 tx12.352mhz_7 af5 txser_7 ae6 txmsync_7 txinclk_7 af6 txsync_7 ae7 rxsync_7 af7 rxtsb4_7 ae8 rxtsb3_7 rx8khz_7 af8 rxtsb2_7 rxtschn_7 ae9 rxtsb1_7 rxfrtd_7 af9 rxtsb0_7 rxsig_7 ae10 txsync_6 af10 txmsync_6 txinclk_6 ae11 txser_6 af11 nc ae12 txtsb2_6 tx12.352mhz_6 af12 txtsb1_6 txfrtd_6 ae13 txtsclk_6 af13 rxmsync_6 rxcrcmsync_6 ae14 nc af14 nc ae15 nc af15 rxtsclk_6 ae16 rxser_6 af16 rxtsb3_6 rx8khz_6 ae17 nc af17 rxtsb1_6 rxfrtd_6 ae18 txtsb4_5 af18 rxoh_6 p in p in n ame p in p in n ame p in p in n ame p in p in n ame
xrt84l38 10 octal t1/e1/j1 framer rev. 1.0.1 ae19 txtsb2_5 tx12.352mhz_5 af19 txtsb1_5 txfrtd_5 ae20 txtsclk_5 af20 txtsb0_5 txsig_5 ae21 rxohclk_5 af21 txmsync_5 txinclk_5 ae22 rxtsb3_5 rx8khz_5 af22 nc ae23 rxser_5 af23 rxtsb2_5 rxtschn_5 ae24 txtsb4_4 af24 nc ae25 nc af25 rxserclk_5 ae26 txtsb2_4 tx12.352mhz_4 af26 txtsb3_4 txohsync_4 p in p in n ame p in p in n ame
xrt84l38 5 rev. 1.0.1 octal t1/e1/j1 framer pin descriptions transmit serial data input (framer channel number indicated by _n) s ignal n ame p in # t ype d escription txser_0 txser_1 txser_2 txser_3 txser_4 txser_5 txser_6 txser_7 b6 a14 b22 f25 ab26 ad19 ae11 af5 i transmit serial data input?transmit framer_n: this input pin along with txserclk_n functions as the transmit serial input port for framer_n. ds1 mode: any payload data applied to this pin would be inserted into a ds1 frame and output onto the t1 line via the txpos_n and txneg_n output pins. if framer_n is configured accordingly, the framing alignment bits, the facility data link bits and the crc-6 bits can also be inserted to input pin.the signal applied to this input pin can be latched to the transmit payload data input interface on either the rising edge or the falling edge of txserclk_n according to configura - tions of framer_n. e1 mode: any payload data applied to this pin would be inserted into an e1 frame and output onto the e1 line via the txpos_n and txneg_n output pins. all data intended to be transported via time slots 1 through 15 and time slots 17 through 31, within each e1 frame, must be applied to this input pin. if framer_n is configured accordingly, data intended for time slots 0 and 16 can also be applied to this input pin.
xrt84l38 6 octal t1/e1/j1 framer rev. 1.0.1 txserclk_0 txserclk_1 txserclk_2 txserclk_3 txserclk_4 txserclk_5 txserclk_6 txserclk_7 d8 a16 d20 g23 y23 ac18 ad9 ac6 i or o transmit serial clock signal --transmit framer_n: this clock signal is used by the transmit payload data input interface, to latch the contents of the txser_n signal into the octal t1/e1/j1 framer ic. data that is applied at the txser_n input is latched into the transmit payload data input interface (for framer_n) on either the rising edge or the falling edge of txserclk_n depending on configurations of framer_n. txserclk_n can either be an input or an output. ds1 mode: transmit back-plane interface-1.544 mhz clock mode if txmuxen = 0 and tximode[1:0] = 00 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 1.544 mbit/s. if the transmit section of framer_n has been configured to use the txserclk_n signal as the timing source, then this signal will be an input . if the transmit section of framer_n has been configured to use either the rxlineclk_n signal or the oscclk signal as the timing source, then txserclk_n will be an output . transmit back-plane interface-high speed clock mode if txmuxen 0 and tximode[1:0] 00 in transmit interface control register, transmit back-plane interface of framer_n is operating at a high-speed mode and is taking data at rates of 2.048 mbit/s, 4.096 mbit/s, 8.192 mbit/s, 12.352 mbit/s or 16.384 mbit/s. the txserclk_n signal will be an input clock signal running at 1.544 mhz. e1 mode: transmit back-plane interface-2.048 mhz clock mode if txmuxen = 0 and tximode[1:0] = 00 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 2.048 mbit/s. if the transmit section of framer_n has been configured to use the txserclk_n signal as the timing source, then this signal will be an input . if the transmit section of framer_n has been configured to use either the rxlineclk_n signal or the oscclk signal as the timing source, then txserclk_n will be an output . transmit back-plane interface-high speed clock mode if txmuxen 0 or tximode[1:0] 00 in transmit interface control register, transmit back-plane interface of framer_n is operating at a high-speed mode. the txserclk_n signal w ill be an i nput clock signal running at 2.048 mhz. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 7 rev. 1.0.1 octal t1/e1/j1 framer txsync_0 txsync_1 txsync_2 txsync_3 txsync_4 txsync_5 txsync_6 txsync_7 d6 a12 a21 e25 aa23 ac19 ae10 af6 i or o single frame sync pulse input/output?transmit framer_n: this pin is configured to be an input if the txserclk_n input pin is configured to be the timing reference for the transmit portion of framer_n. this pin is configured as an output if the rxlineclk_n input pin or the oscclk input pins are configured to be the timing reference for the transmit portion of framer_n. ds1 mode: when pin is configured to be an input if this pin is configured to be an input , then the user must pulse this pin "high" for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the first bit (f-bit) of an outbound ds1 frame. n ote : it is imperative that the txsync_n input signal be synchronized with the txserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output , then it will pulse "high", for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the last payload bit within an outbound ds1 frame. e1 mode: when pin is configured to be an input if this pin is configured to be an input , then the user must pulse this pin "high" for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the international bit (si) of an outbound e1 frame. n ote : it is imperative that the txsync_n input signal be synchronized with the txserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output , then it will pulse "high", for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the last bit within a given outbound e1 frame. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 8 octal t1/e1/j1 framer rev. 1.0.1 txmsync_0 txmsync_1 txmsync_2 txmsync_3 txmsync_4 txmsync_5 txmsync_6 txmsync_7 c6 b13 a22 f26 ac26 af21 af10 ae6 i or o multiframe sync pulse input/output?framer_n: this signal indicates the boundary of an outbound multi-frame. ds1 mode: transmit back-plane interface-1.544 mhz clock mode if txmuxen = 0 and tximode[1:0] = 00 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 1.544 mbit/s. this pin is configured to be an input if the txserclk_n input pin is con - figured to be the timing reference for the transmit section of framer_n. con - versely, this pin will be configured as an output if the rxlineclk input pin or the oscclk input pins are configured to be the timing reference for the trans - mit section of framer_n.the roles of these pins when configured as input or output, is described below. when pin is configured to be an input if this pin is configured to be an input , this pin must be pulsed "high" for one period of txserclk_n, the instant that the transmit payload data interface (of framer_n) is processing the first bit of a ds1 multi-frame. n ote : it is imperative that the txmsync_n input signal be synchronized with the txserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output , then it will pulse "high", for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the last bit of a ds1 multi-frame. e1 mode: transmit back-plane interface-2.048 mhz clock mode if txmuxen = 0 and tximode[1:0] = 00 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 2.048 mbit/s. this pin is configured to be an input if the txserclk_n input pin is con - figured to be the timing reference for the transmit section of framer_n. con - versely, this pin will be configured as an output if the rxlineclk input pin or the oscclk input pins are configured to be the timing reference for the trans - mit section of framer_n. when pin is configured to be an input if this pin is configured to be an input, this pin must be pulsed "high" for one period of txserclk_n, the instant that the transmit payload data interface (of framer_n) is processing the first international bit (si) of an "outbound" crc payload data multiframe. n otes : 1. this pin is ignored if crc multiframe alignment has been disabled. 2. it is imperative that the txmsync_n input signal be synchronized with the txserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output, then it will pulse "high", for one period of txserclk_n, when the transmit payload data input interface (of framer_n) is processing the last bit, within an "outbound" crc multi-frame. n otes : 1. this pin is inactive if crc multi-frame alignment has been disabled. 2. the purpose of this output pin is to permit the terminal equipment to maintain alignment with the "outbound" crc-multi-frame structure. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 9 rev. 1.0.1 octal t1/e1/j1 framer txinclk_0 txinclk_1 txinclk_2 txinclk_3 txinclk_4 txinclk_5 txinclk_6 txinclk_7 c6 b13 a22 f26 ac26 af21 af10 ae6 i transmit input clock signal -- transmit framer _n if txmuxen 0 or tximode[1:0] 00 in transmit interface control register, transmit back-plane interface of framer_n is operating at a high-speed mode. this pin will function as an input clock signal for the high-speed transmit back- plane interface. ds1 mode: transmit back-plane interface-mvip, 2.048 mhz clock mode if txmuxen = 0 and tximode[1:0] = 01 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 2.048 mbit/s. the txinclk_n signal will be an input clock signal running at 2.048 mhz. transmit back-plane interface-4.096 mhz clock mode if txmuxen = 0 and tximode[1:0] = 10 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 4.096 mbit/s. the txinclk_n signal will be an input clock signal running at 4.096 mhz. transmit back-plane interface-8.192 mhz clock mode if txmuxen = 0 and tximode[1:0] = 11 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 8.192 mbit/s. the txinclk_n signal will be an input clock signal running at 8.192 mhz. transmit back-plane interface-multiplexed at 12.352 mhz clock mode if txmuxen = 1 and tximode[1:0] = 00 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 12.352 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 12.352 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. transmit back-plane interface-multiplexed at 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 01 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. transmit back-plane interface-hmvip, 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 10 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 10 octal t1/e1/j1 framer rev. 1.0.1 txinclk_0 txinclk_1 txinclk_2 txinclk_3 txinclk_4 txinclk_5 txinclk_6 txinclk_7 c6 b13 a22 f26 ac26 af21 af10 ae6 i transmit input clock signal -- transmit framer _n (continued) transmit back-plane interface-h.100, 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 11 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. e1 mode: transmit back-plane interface-2.048 mhz clock mode if txmuxen = 0 and tximode[1:0] = 01 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 2.048 mbit/s. the txinclk_n signal will be an input clock signal running at 2.048 mhz. transmit back-plane interface-4.096 mhz clock mode if txmuxen = 0 and tximode[1:0] = 10 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 4.096 mbit/s. the txinclk_n signal will be an input clock signal running at 4.096 mhz. transmit back-plane interface-8.192 mhz clock mode if txmuxen = 0 and tximode[1:0] = 11 in transmit interface control register, transmit back-plane interface of framer_n is taking data at a rate of 8.192 mbit/s. the txinclk_n signal will be an input clock signal running at 8.192 mhz. transmit back-plane interface-multiplexed at 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 01 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. transmit back-plane interface-hmvip, 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 10 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 11 rev. 1.0.1 octal t1/e1/j1 framer txinclk_0 txinclk_1 txinclk_2 txinclk_3 txinclk_4 txinclk_5 txinclk_6 txinclk_7 c6 b13 a22 f26 ac26 af21 af10 ae6 i transmit input clock signal -- transmit framer _n (continued) transmit back-plane interface-h.100, 16.384 mhz clock mode if txmuxen = 1 and tximode[1:0] = 11 in transmit interface control register, transmit back-plane interface of framer_n is taking multiplexed data at a rate of 16.384 mbit/s. txinclk_0 and txinclk_4 signals will be input clock signals running at 16.384 mhz. txinclk_1, 2, 3 and txinclk_5, 6, 7 signals are not required. transmit payload data of channel 0, 1, 2 and 3 are multiplexed and latched into transmit back-plane interface using clock edge of txinclk_0 via txser_0 input pin. transmit payload data of channel 4, 5, 6 and 7 are multi - plexed and latched into transmit back-plane interface using clock edge of txinclk_4 via txser_4 input pin. inside the octal framer, data will be de-multi - plexed into 8 channels from the serial inputs of channel 0 and 4. txtsb0_0 txtsb0_1 txtsb0_2 txtsb0_3 txtsb0_4 txtsb0_5 txtsb0_6 txtsb0_7 txsig_0 txsig_1 txsig_2 txsig_3 txsig_4 txsig_5 txsig_6 txsig_7 c8 d15 a23 g24 ab24 af20 ac13 ac7 c8 d15 a23 g24 ab24 af20 ac13 ac7 o i transmit framer_n--time slot octet identifier output-bit [0:4]: these output signals (txtsb4_n through txtsb0_n) reflects the five-bit binary value of the number of time slot (in the incoming ds1 frame), being accepted and processed by the transmit payload data input interface block associated with framer_n. terminal equipment should use the txtsclk_n clock signal to sample the five output pins of each channel in order to identify the time-slot being processed by the transmit payload data input interface block of framer_n. transmit serial signaling input--transmit framer_n these pins can be used to input robbed-bit signaling data within an outbound ds1 frame or to input channel associated signaling (cas) bits within an out - bound e1 frame, if framer_n is configured accordingly. txtsb1_0 txtsb1_1 txtsb1_2 txtsb1_3 txtsb1_4 txtsb1_5 txtsb1_6 txtsb1_7 txfrtd_0 txfrtd_1 txfrtd_2 txfrtd_3 txfrtd_4 txfrtd_5 txfrtd_6 txfrtd_7 d9 b15 c22 h23 ac24 af19 af12 ad6 d9 b15 c22 h23 ac24 af19 af12 ad6 o i transmit framer_n--time slot octet identifier output-bit 1: these output signals (txtsb4_n through txtsb0_n) reflects the five-bit binary value of the number of time slot (in the incoming ds1 frame), being accepted and processed by the transmit payload data input interface block associated with framer_n. terminal equipment should use the txtsclk_n clock signal to sample the five output pins of each channel in order to identify the time-slot being processed by the transmit payload data input interface block of framer_n. transmit serial fractional t1/e1 input--transmit framer_n these pins can be used to input fractional ds1/e1 payload data within an out - bound ds1/e1 frame, if framer_n is configured accordingly. in this mode, ter - minal equipment will use either txtsclk_n or txserclk_n output pins to clock out fractional ds1/e1 payload data. framer_n will then use txtsclk_n or txserclk_n to clock in fractional ds1/e1 payload data. please see pin description of txtsclk_n for details. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 12 octal t1/e1/j1 framer rev. 1.0.1 txtsb2_0 txtsb2_1 txtsb2_2 txtsb2_3 txtsb2_4 txtsb2_5 txtsb2_6 txtsb2_7 tx12.352mhz_0 tx12.352mhz_1 tx12.352mhz_2 tx12.352mhz_3 tx12.352mhz_4 tx12.352mhz_5 tx12.352mhz_6 tx12.352mhz_7 a8 a15 b23 j23 ae26 ae19 ae12 ae5 a8 a15 b23 j23 ae26 ae19 ae12 ae5 o o transmit framer_n--time slot octet identifier output-bit 2: these output signals (txtsb4_n through txtsb0_n) reflects the five-bit binary value of the number of time slot (in the incoming ds1 frame) being accepted and processed by the transmit payload data input interface block associated with framer_n. terminal equipment should use the txtsclk_n clock signal to sample the five output pins of each channel in order to identify the time-slot being processed by the transmit payload data input interface block of framer_n. if txtsb1_n pin is configured as txfrtd_n to input fractional ds1 payload data into framer_n, the txtsb2_n pin will serially output the five-bit binary value of the number of the time slot being accepted and processed by the transmit payload data input interface block associated with framer_n. transmit 12.352mhz clock output-transmit framer_n: these pins can be used to output 12.352mhz clock derived from oscclk, if framer_n is configured accordingly. txtsb3_0 txtsb3_1 txtsb3_2 txtsb3_3 txtsb3_4 txtsb3_5 txtsb3_6 txtsb3_7 txohsync_0 txohsync_1 txohsync_2 txohsync_3 txohsync_4 txohsync_5 txohsync_6 txohsync_7 b8 d16 a24 h24 af26 ad18 ac12 af4 b8 d16 a24 h24 af26 ad18 ac12 af4 o o transmit framer_n-time slot octet identifier output-bit 3: these output signals (txtsb4_n through txtsb0_n) reflects the five-bit binary value of the number of time slot (in the incoming ds1 frame) being accepted and processed by the transmit payload data input interface block associated with framer_n. terminal equipment should use the txtsclk_n clock signal to sample the five output pins of each channel in order to identify the time-slot being processed by the transmit payload data input interface block of framer_n. transmit overhead synchronization pulse--transmit framer_n: these pins can be used to output overhead synchronization pulse that indi - cate the first bit of each multi-frame, if framer_n is configured accordingly. txtsb4_0 txtsb4_1 txtsb4_2 txtsb4_3 txtsb4_4 txtsb4_5 txtsb4_6 txtsb4_7 c10 c17 d22 j25 ae24 ae18 ad11 ae4 o transmit framer_n--time slot octet identifier output-bit 4: these output signals (txtsb4_n through txtsb0_n) reflects the five-bit binary value of the number of time slot (in the incoming ds1 frame) being accepted and processed by the transmit payload data input interface block associated with framer_n. terminal equipment should use the txtsclk_n clock signal to sample the five output pins of each channel in order to identify the time-slot being processed by the transmit payload data input interface block of framer_n. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 13 rev. 1.0.1 octal t1/e1/j1 framer txtsclk_0 txtsclk_1 txtsclk_2 txtsclk_3 txtsclk_4 txtsclk_5 txtsclk_6 txtsclk_7 d10 b14 c21 d25 ab25 ae20 ae13 ac5 o transmit channel clock output signal?framer_n: this pin indicates the boundary of each time slot of an outbound ds1/e1 frame. ds1 mode: each of these output pins are a 192khz clock output which pulses "high" whenever the transmit payload data input interface block accepts the lsb of each of the 24 time slots, within the ds1 data stream, being processed via framer _n. the terminal equipment should use this clock signal to sample the txtsb0_n through txtsb4_n output signals and identify the time-slot being processed via the "transmit section" of each framer_n. if txtsb1_n pin is configured as txfrtd_n to input fractional ds1 payload data into framer_n, the txtsclk_n pin can be configured to function as one of the following: the pin will output gaped fractional ds1 clock that can be used by terminal equipment to clock out fractional ds1 payload data at rising edge of the clock. framer_n will then input fractional ds1 payload data using falling edge of the clock.otherwise, this pin will be a clock enable signal to transmit fracti onal ds1 input (txfrtd_n) if framer_n is configured accordingly. in this mode, fractional ds1 payload data is clocked into the chip using un-gaped txserclk_n. e1 mode: each of these output pins are a 256khz clock output which pulses "high" whenever the transmit payload data input interface block accepts the lsb of each of the 32 time slots, within the e1 data stream, being processed via framer _n. the terminal equipment should use this clock signal to sample the txtsb0_n through txtsb4_n output signals, and identify the time-slot being processed via the "transmit section" of each framer_n. if txtsb1_n pin is configured as txfrtd_n to input fractional e1 payload data into framer_n, the txtsclk_n pin can be configured to function as one of the following: the pin will output gaped fractional e1 clock that can be used by ter - minal equipment to clock out fractional e1 payload data at rising edge of the clock. framer_n will then input fractional e1 payload data using falling edge of the clock.otherwise, this pin will be a clock enable signal to transmit fractional e1 input (txfrtd_n) if framer_n is configured accordingly. in this mode, frac - tional e1 payload data is clocked into the chip using un-gaped txserclk_n. transmit serial data input (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 14 octal t1/e1/j1 framer rev. 1.0.1 overhead interface (framer channel number indicated by _n) s ignal n ame p in # t ype d escription txoh_0 txoh_1 txoh_2 txoh_3 txoh_4 txoh_5 txoh_6 txoh_7 a7 c14 d23 f23 aa24 ac17 ac14 ad5 i transmit overhead input?framer_n: this input pin, along with txohclk_n functions as the transmit overhead input port for framer_n. ds1 mode: this input pin will become active if the transmit section of framer_n has been configured to use this input as the source of facility data link bits in esf fram - ing mode, fs bits in the slc96 and n framing mode, and r bit in t1dm mode. the data that is input into this pin will be inserted into the data link bits within the outbound ds1 frames at the falling edge of txohclk_n. n ote : this input pin will be disabled if framer_n is using the transmit hdlc controller, or the txser_n input as the source for the data link bits. e1 mode: this input pin will become active if the transmit section of framer_n has been configured to use this input as the source of data link bits. the data that is input into this pin will be inserted into the sa4 through sa8 bits (the national bits) within the outbound non-fas e1 frames. n ote : this input pin will be disabled if framer_n is using the transmit hdlc controller, or the txser_n input as the source for the data link bits. txohclk_0 txohclk_1 txohclk_2 txohclk_3 txohclk_4 txohclk_5 txohclk_6 txohclk_7 a5 c15 d21 f24 ac25 ad20 ad13 af3 o transmit oh serial clock output signal?framer_n: this output clock signal functions as a demand clock signal for the "transmit overhead data input interface" block associated with framer_n. ds1 mode: if the "transmit overhead data input interface" has been configured to be the source of facility data link bits in esf framing mode, fs bits in the slc96 and n framing mode, and r bit in t1dm framing mode, then the transmit overhead data input interface block will provide a clock edge for each data link bit. data link equipment, which is interfaced to this pin, should update its data (on the txoh_n line) on the rising edge of this clock signal. the transmit overhead data input interface will latch the data (on the txoh_n line) on the falling edge of this clock signal. n otes : 1. if the "transmit overhead data input interface? has not been configured to be the source of the data link information, then this output signal will be inactive. 2. depending on the configurations of framer_n, the clock frequency in esf framing mode can be 2khz or 4khz in esf. e1 mode: if the "transmit overhead data input interface" has been configured to be the source of data link information, then the transmit overhead data input inter - face block will provide a clock edge for each "sa" bit that is carrying data link information. data link equipment, which is interfaced to this pin, should update its data (on the txoh_n line) on the rising edge of this clock signal. the transmit overhead data input interface will latch the data (on the txoh_n line) on the falling edge of this clock signal. n ote : if the "transmit overhead data input interface? has not been configured to be the source of the data link information, then this output signal will be inac - tive.
xrt84l38 15 rev. 1.0.1 octal t1/e1/j1 framer rxoh_0 rxoh_1 rxoh_2 rxoh_3 rxoh_4 rxoh_5 rxoh_6 rxoh_7 c7 b10 c19 b26 w25 ac20 af18 ac11 o receive overhead output?framer_n: this pin, along with rxohclk_n functions as the receive overhead output interface for framer_n. ds1 mode: this pin unconditionally outputs the contents of the facility data link bit in esf framing mode, fs bit in the slc96 and n framing mode, and r bit in t1dm framing mode. n ote : this output pin is active even if the receive hdlc controller (within framer_n) is active. e1 mode: this pin unconditionally outputs the contents of the national bits (the "sa4" through the "sa8" bits). if framer_n has been configured to interpret the national bits of the incoming e1 frames as carrying "data link" information; then the receive overhead output interface will provide a clock pulse (via the rxohclk_n output pin) for each "sa" bit carrying data link information. n ote : this output pin is active even if the receive hdlc controller (within framer_n) is active. rxohclk_0 rxohclk_1 rxohclk_2 rxohclk_3 rxohclk_4 rxohclk_5 rxohclk_6 rxohclk_7 c5 b12 d19 b25 v23 ae21 ad17 ad10 o receive oh serial clock output signal?framer_n: this pin, along with rxoh_n functions as the receive overhead output inter - face for framer_n. ds1 mode: this pin outputs a clock edge corresponding to each facility data link bit in esf framing mode, fs bit in the slc96 and n framing mode, and r bit in t1dm framing mode, which carries data link information. n otes : 1. depending on the configurations of framer_n, the clock frequency in esf framing mode can be 2khz or 4khz. 2. this output pin is inactive if the receive hdlc controller (within framer_n) has been enabled. e1 mode: this pin outputs a clock edge corresponding to each national bit that is carrying "data link" information. n ote : this output pin is inactive if the receive hdlc controller (within framer_n) has been enabled. overhead interface (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 16 octal t1/e1/j1 framer rev. 1.0.1 receive serial data output (framer channel number indicated by _n) s ignal n ame p in # t ype d escription rxsync_0 rxsync_1 rxsync_2 rxsync_3 rxsync_4 rxsync_5 rxsync_6 rxsync_7 a3 b11 b16 c24 v26 ac22 ad14 ae7 i or o single frame sync pulse input/output pin?receive framer_n: this pin is configured to be an input if the slip buffer associated with framer_n is enabled. conversely, this pin will be configured to be an output if the slip- buffer is by-passed. ds1 mode: when pin is configured to be an input if this pin is configured to be an input, then the user must pulse this pin "high" for one period of rxserclk_n, when the receive payload data output interface (of framer_n) is processing the first bit (f-bit) of an inbound ds1 frame. n ote : it is imperative that the rxsync_n input signal be synchronized with the rxserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output, then it will pulse "high", for one period of rxserclk_n, when the receive payload data output interface (of framer_n) is processing the first bit (f-bit) of an inbound ds1 frame. e1 mode: when pin is configured to be an input if this pin is configured to be an input, then this pin must be pulsed "high" for one period of rxserclk_n, when the receive e1 serial (or overhead) output interface, outputs the international bit (si) of an inbound e1 frame. n ote : it is imperative that the rxsync_n input signal be synchronized with the rxserclk_n input signal. when pin is configured to be an output if this pin is configured to be an output, then it will pulse "high" for one period of rxserclk_n, when the receive e1 serial (or overhead) output interface outputs the last bit, in an inbound e1 frame. rxmsync_0 rxmsync_1 rxmsync_2 rxmsync_3 rxmsync_4 rxmsync_5 rxmsync_6 rxmsync_7 rxcrcmsync_0 rxcrcmsync_1 rxcrcmsync_2 rxcrcmsync_3 rxcrcmsync_4 rxcrcmsync_5 rxcrcmsync_6 rxcrcmsync_7 b3 c9 a19 a26 v25 ad24 af13 ac8 b3 c9 a19 a26 v25 ad24 af13 ac8 o o multiframe sync pulse output--receive framer_n: this ds1-only signal will pulse "high" for one period of rxserclk_n, the instant that the receive payload data interface (of framer_n) is processing the first bit of a ds1 multi-frame. receive "crc multiframe" sync output signal-framer_n: this e1-only signal pulses "high" for one period of rxserclk_n whenever the receive e1 output interface of framer_n outputs the first bit, within a given "crc multiframe". n ote : this output pin is inactive if crc multiframe alignment is disabled.
xrt84l38 17 rev. 1.0.1 octal t1/e1/j1 framer rxserclk_0 rxserclk_1 rxserclk_2 rxserclk_3 rxserclk_4 rxserclk_5 rxserclk_6 rxserclk_7 b2 b9 a17 e23 u24 af25 ad15 ad7 i or o receive serial clock signal?receive framer_n: this signal is used by the receive payload data output interface, to latch the contents of the rxser_n signal out from the octal t1/e1/j1 framer ic. framer_n can use either the rising edge or the falling edge of rxserclk_n sig - nal to latch the received ds1 payload data out. depending on configurations of framer_n. rxserclk_n can either be an input or an output. ds1 mode: receive back-plane interface-1.544 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 00 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 1.544 mbit/s. this pin is configured to be an input if the slip buffer associated with framer_n is enabled. conversely, this pin will be configured to be an output if the "slip-buffer" is "by-passed". receive back-plane interface-mvip, 2.048 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 01 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 2.048 mbit/s. the rxserclk_n signal will be an input clock signal running at 2.048 mhz. receive back-plane interface-4.096 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 10 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 4.096 mbit/s. the rxserclk_n signal will be an input clock signal running at 4.096 mhz. receive back-plane interface-8.192 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 11 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 8.192 mbit/s. the rxserclk_n signal will be an input clock signal running at 8.192 mhz. receive back-plane interface-multiplexed at 12.352 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 00 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 12.352 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 12.352 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 18 octal t1/e1/j1 framer rev. 1.0.1 rxserclk_0 rxserclk_1 rxserclk_2 rxserclk_3 rxserclk_4 rxserclk_5 rxserclk_6 rxserclk_7 b2 b9 a17 e23 u24 af25 ad15 ad7 i or o receive serial clock signal?receive framer_n: (continued) receive back-plane interface-multiplexed at 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 01 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. receive back-plane interface-hmvip, 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 10 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. receive back-plane interface-h.100, 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 11 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. e1 mode: receive back-plane interface-2.048 mhz (xrt84v24 compatible) clock mode if rxmuxen = 0 and rximode[1:0] = 00 in receive interface control register, receive back-plane interface of framer_n is presenting data at a xrt84v24 compatible rate of 2.048 mbit/s. this pin is configured to be an input if the slip buffer associated with framer_n is enabled. conversely, this pin will be config - ured to be an output if the "slip-buffer" is "by-passed". receive back-plane interface-2.048 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 01 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 2.048 mbit/s. the rxserclk_n signal will be an input clock signal running at 2.048 mhz. receive back-plane interface-4.096 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 10 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 4.096 mbit/s. the rxserclk_n signal will be an input clock signal running at 4.096 mhz. receive back-plane interface-8.192 mhz clock mode if rxmuxen = 0 and rximode[1:0] = 11 in receive interface control register, receive back-plane interface of framer_n is presenting data at a rate of 8.192 mbit/s. the rxserclk_n signal will be an input clock signal running at 8.192 mhz. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 19 rev. 1.0.1 octal t1/e1/j1 framer rxserclk_0 rxserclk_1 rxserclk_2 rxserclk_3 rxserclk_4 rxserclk_5 rxserclk_6 rxserclk_7 b2 b9 a17 e23 u24 af25 ad15 ad7 i or o receive serial clock signal?receive framer_n: (continued) receive back-plane interface-multiplexed at 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 01 in receive interface control register, receive back-plane interface of framer_n is presenting bit-multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. receive back-plane interface-hmvip, 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 10 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. receive back-plane interface-h.100, 16.384 mhz clock mode if rxmuxen = 1 and rximode[1:0] = 11 in receive interface control register, receive back-plane interface of framer_n is presenting multiplexed data at a rate of 16.384 mbit/s. rxserclk_0 and rxserclk_4 signals will be input clock signals running at 16.384 mhz. rxserclk_1, 2, 3 and rxserclk_5, 6, 7 signals are not required. received ds1 payload data of channel 0, 1, 2 and 3 are mul - tiplexed and latched out from receive back-plane interface using clock edge of rxserclk_0 via rxser_0 output pin. receive ds1 payload data of channel 4, 5, 6 and 7 are multiplexed and latched out from receive back-plane interface using clock edge of rxserclk_4 via rxser_4 output pin. rxser_0 rxser_1 rxser_2 rxser_3 rxser_4 rxser_5 rxser_6 rxser_7 d4 a9 c18 b24 w26 ae23 ae16 ad8 o receive serial data output?receive framer_n: this output pin along with rxserclk_n functions as the receive serial output port for framer_n. t1 mode: any incoming t1 line data that is received from the rxpos_n and rxneg_n input pins, will be decoded and output via this pin.framer_n can use either the rising edge or the falling edge of rxserclk_n input pin to latch the received t1 payload data out according to configurations of framer_n. e1 mode: much of the data that is received from the line via the rxpos_n and rxneg_n input pins, will be decoded and output via this pin, in a binary format.all data that is transported via time slots 1 through 15 and time slots 17 through 31, within each incoming e1 frame, will be output via this pin. if framer_n is configured accordingly, the data for time slots 0 and 16 will also be output via this pin. framer_n can use either the rising edge or the falling edge of rxserclk_n input pin to latch the received ds1/e1 payload data out according to configurations of framer_n. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 20 octal t1/e1/j1 framer rev. 1.0.1 rxtsb0_0 rxtsb0_1 rxtsb0_2 rxtsb0_3 rxtsb0_4 rxtsb0_5 rxtsb0_6 rxtsb0_7 rxsig_0 rxsig_1 rxsig_2 rxsig_3 rxsig_4 rxsig_5 rxsig_6 rxsig_7 a2 d12 a18 c25 w24 ad22 ac16 af9 a2 d12 a18 c25 w24 ad22 ac16 af9 o o receive framer_n--time slot octet identifier output-bit 0: these output signals (rxtsb4_n through rxtsb0_n) reflect the five-bit binary value of the number of time slot (in the incoming ds1 frame) being received and output to the terminal equipment via the receive payload data output interface block associated with framer_n. the terminal equipment should use the rxtsclk_n clock to sample these five output pins in order to identify the time-slot being processed by the receive section of framer_n. receive serial signaling output--receive framer_n: these pins can be used to output robbed-bit signaling data extracted from an incoming ds1 frame, if framer_n is configured accordingly. rxtsb1_0 rxtsb1_1 rxtsb1_2 rxtsb1_3 rxtsb1_4 rxtsb1_5 rxtsb1_6 rxtsb1_7 rxfrtd_0 rxfrtd_1 rxfrtd_2 rxfrtd_3 rxfrtd_4 rxfrtd_5 rxfrtd_6 rxfrtd_7 d5 a10 b19 c26 y26 ac21 af17 ae9 d5 a10 b19 c26 y26 ac21 af17 ae9 o o receive framer_n--time slot octet identifier output-bit 1: these output signals (rxtsb4_n through rxtsb0_n) reflect the five-bit binary value of the number of time slot (in the incoming ds1 frame) being received and output to the terminal equipment via the receive payload data output interface block associated with framer_n. the terminal equipment should use the rxtsclk_n clock to sample these five output pins in order to identify the time-slot being processed by the receive section of framer_n. receive serial fractional t1/e1 input--receive framer_n: these pins can be used to output fractional ds1/e1 payload data extracted from an inbound ds1/e1 frame, if framer_n is configured accordingly. in this mode, terminal equipment will use either rising edge of rxtsclk_n or rxserclk_n to clock in fractional ds1/e1 payload data. please see pin description of rxtsclk_n for details. rxtsb2_0 rxtsb2_1 rxtsb2_2 rxtsb2_3 rxtsb2_4 rxtsb2_5 rxtsb2_6 rxtsb2_7 rxtschn_0 rxtschn_1 rxtschn_2 rxtschn_3 rxtschn_4 rxtschn_5 rxtschn_6 rxtschn_7 b4 c11 b20 e24 y25 af23 ad16 af8 b4 c11 b20 e24 y25 af23 ad16 af8 o o receive framer_n--time slot octet identifier output-bit 2: these output signals (rxtsb4_n through rxtsb0_n) reflect the five-bit binary value of the number of time slot (in the incoming ds1 frame) being received and output to the terminal equipment via the receive payload data output interface block associated with framer_n. the terminal equipment should use the rxtsclk_n clock to sample these five output pins in order to identify the time-slot being processed by the receive section of framer_n. receive framer_n -- time slot identifier serial output if rxtsb1_n pin is configured as rxfrtd_n to output fractional ds1 payload data from framer_n, then these pins serially output the five-bit binary value of the number of the time slot being accepted and processed by the transmit payload data input interface block associated with framer_n. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 21 rev. 1.0.1 octal t1/e1/j1 framer rxtsb3_0 rxtsb3_1 rxtsb3_2 rxtsb3_3 rxtsb3_4 rxtsb3_5 rxtsb3_6 rxtsb3_7 rx8khz_0 rx8khz_1 rx8khz_2 rx8khz_3 rx8khz_4 rx8khz_5 rx8khz_6 rx8khz_7 b5 d13 c20 d26 w23 ae22 af16 ae8 b5 d13 c20 d26 w23 ae22 af16 ae8 o o receive framer_n-time slot octet identifier output-bit 3: these output signals (rxtsb4_n through rxtsb0_n) reflect the five-bit binary value of the number of time slot (in the incoming ds1 frame) being received and output to the terminal equipment via the receive payload data output interface block associated with framer_n. the terminal equipment should use the rxtsclk_n clock to sample these five output pins in order to identify the time-slot being processed by the receive section of framer_n. receive 8khz clock-receive framer_n: these pins output a reference 8khz signal clock as if framer_n is configured accordingly. rxtsb4_0 rxtsb4_1 rxtsb4_2 rxtsb4_3 rxtsb4_4 rxtsb4_5 rxtsb4_6 rxtsb4_7 d7 a13 b21 e26 aa26 ad21 ac15 af7 o receive framer_n--time slot octet identifier output-bit 4: these output signals (rxtsb4_n through rxtsb0_n) reflect the five-bit binary value of the number of time slot (in the incoming ds1 frame) being received and output to the terminal equipment via the receive payload data output interface block associated with framer_n. the terminal equipment should use the rxtsclk_n clock to sample these five output pins in order to identify the time-slot being processed by the receive section of framer_n. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 22 octal t1/e1/j1 framer rev. 1.0.1 rxtsclk_0 rxtsclk_1 rxtsclk_2 rxtsclk_3 rxtsclk_4 rxtsclk_5 rxtsclk_6 rxtsclk_7 c4 d11 d18 a25 v24 ad25 af15 ac9 o receive channel clock output signal?framer_n: this pin indicates the boundary of each time slot of an inbound ds1/e1 frame. ds1 mode: each of these output pins are a 192khz clock output which pulses "high" when - ever the receive payload data output interface block outputs the lsb of each of the 24 time slots (within the inbound ds1 data stream) on the rxser_n pin. the terminal equipment should use this clock signal to sample the rxtsb0_n through rxtsb4_n output signals, and identify the time-slot being processed via the "receive section" of each framer_n. if rxtsb1_n pin is configured as rxfrtd_n to output fractional ds1 payload data from framer_n, the rxtsclk_n pin can be configured to function as one of the following: the pin will output gaped fractional ds1 clock that can be used by terminal equipment to clock out fractional ds1 payload data at rising edge of the clock. otherwise, this pin will be a clock enable signal to receive fractional ds1 out - put (rxfrtd_n) if framer_n is configured accordingly. in this mode, fractional ds1 payload data is clocked into the terminal equipment using un-gapped rxserclk_n. e1 mode: each of these output pins are a 256khz clock output which pulses "high" when - ever the receive payload data output interface block outputs the lsb of each of the 32 time slots (within the inbound e1 data stream) on the rxser_n pin. the terminal equipment should use this clock signal to sample the rxtsb0_n through rxtsb4_n output signals, and identify the time-slot being processed via the "receive section" of each framer_n. if rxtsb1_n pin is configured as rxfrtd_n to output fractional e1 payload data from framer_n, the rxtsclk_n pin can be configured to function as one of the following: the pin will output gaped fractional e1 clock that can be used by ter - minal equipment to clock out fractional e1 payload data at rising edge of the clock. otherwise, this pin will be a clock enable signal to receive fractional e1 output (rxfrtd_n) if framer_n is configured accordingly. in this mode, fractional e1 payload data is clocked into the terminal equipment using un-gaped rxserclk_n. rxlos_0 rxlos_1 rxlos_2 rxlos_3 rxlos_4 rxlos_5 rxlos_6 rxlos_7 d2 h4 j1 l4 u1 y1 aa3 ab4 o receive loss of signal output indicator?framer_n: this output pin will toggle ?high? (declare los) if the receive block associated with framer_n determines that neither the rxpos_n or the rxneg_n inputs have received a high level pulse in the last 32 bit periods. this output pin will toggle ?low? if the receive block, associated with framer_n, detects a string of 32 consecutive bits, that does not contain a string of 4 con - secutive ?0?s?. n ote : this output pin will also toggle "high" if the los_0 input pin is asserted (e.g., toggled ?high? by the liu los output pin). rxcasmsync_0 rxcasmsync_1 rxcasmsync_2 rxcasmsync_3 rxcasmsync_4 rxcasmsync_5 rxcasmsync_6 rxcasmsync_7 a4 a11 b18 d24 y24 ad23 ad12 ac10 o receive ?cas multiframe? sync output signal--framer_n: this e1-only signal pulses "high" for one period of rxserclk_n whenever the receive e1 output interface of framer_n outputs the first bit, within a given "cas multiframe". n ote : this output pin is inactive if common channel signaling is enabled. receive serial data output (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 23 rev. 1.0.1 octal t1/e1/j1 framer receive decoder liu interface (framer channel number indicated by _n) s ignal n ame p in # t ype d escription rxpos_0 rxpos_1 rxpos_2 rxpos_3 rxpos_4 rxpos_5 rxpos_6 rxpos_7 e4 g3 h1 l2 r2 w2 aa2 ac2 i receive positive polarity pulse?framer_n: this input pin is intended to be connected to the rxpos or rpdata output of the liu (line interface unit) ic associated with framer_n. the liu will assert this input signal (pulse it "high"), when it is receiving a posi - tive-polarity pulse from the line. this input signal is sampled and latched into the framer, on the user-selectable edge (rising or falling) of the rxlineclk_n signal. rxneg_0 rxneg_1 rxneg_2 rxneg_3 rxneg_4 rxneg_5 rxneg_6 rxneg_7 c1 f1 j3 l3 t2 w1 ab1 ad1 i receive negative polarity pulse?framer_n: this input pin is intended to be connected to the rxneg or rndata output of the liu (line interface unit) associated with framer_n. the liu will assert this input signal (pulse it "high"), when it is receiving a nega - tive-polarity pulse from the line. this input signal is sampled and latched into the framer, on the user-selectable edge (rising or falling) of the rxlineclk_n signal. rxlineclk_0 rxlineclk_1 rxlineclk_2 rxlineclk_3 rxlineclk_4 rxlineclk_5 rxlineclk_6 rxlineclk_7 d1 g1 k4 m4 t3 w4 aa4 ae2 i receive line clock input?framer_n: this input pin is intended to be connected to the rxclk output of the liu (line interface unit) associated with framer_n. framer_n uses the user-selectable edge of this signal to sample and latch the signals at the rxpos_n and rxneg_n input pins. transmit encoder liu interface (framer channel number indicated by _n) s ignal n ame p in # t ype d escription txpos_0 txpos_1 txpos_2 txpos_3 txpos_4 txpos_5 txpos_6 txpos_7 txnrz_0 txnrz_1 txnrz_2 txnrz_3 txnrz_4 txnrz_5 txnrz_6 txnrz_7 e3 h3 k3 l1 t4 w3 ab2 ad2 e3 h3 k3 l1 t4 w3 ab2 ad2 o transmit positive polarity pulse?framer_n: this output pin is intended to be connected to the txpos or tpdata input of the liu (line interface unit) associated with framer_n. framer_n will assert this signal when it wishes for the line interface unit (liu) associated with framer_n, to transmit a positive polarity pulse on the line. transmit non return to zero: unipolar output for transmitted data. txnrz_n includes the results of bit 7 stuff - ing, but does not include hdb3 encoding. o
xrt84l38 24 octal t1/e1/j1 framer rev. 1.0.1 txneg_0 txneg_1 txneg_2 txneg_3 txneg_4 txneg_5 txneg_6 txneg_7 txmx_0 txmx_1 txmx_2 txmx_3 txmx_4 txmx_5 txmx_6 txmx_7 f3 h2 k2 m3 v1 y2 ac1 ae1 f3 h2 k2 m3 v1 y2 ac1 ae1 o transmit negative polarity pulse?framer_n: this output pin is intended to be connected to the txneg or tndata input of the liu (line interface unit) associated with framer_n. framer_n will assert this signal when it wishes for the line interface unit (liu) associated with framer_n, to transmit a negative polarity pulse on the line. transmit max output pulses ?high? for one bit time and is coincident with the sampling of the least serial bit of a multiframe. o txlineclk_0 txlineclk_1 txlineclk_2 txlineclk_3 txlineclk_4 txlineclk_5 txlineclk_6 txlineclk_7 f2 g2 j2 n4 v4 y3 ac3 ac4 o transmit line clock output?framer_n: this output pin is intended to be connected to the txclk input of the liu (line interface unit) associated with framer_n. the liu uses this pin to sample and latch the signals at its tpdata and tndata input pins. timing (framer channel number indicated by _n) s ignal n ame p in # t ype d escription oscclk t1 i oscillator clock: this is a programmable operation clock input. this clock input can be one of six frequencies: e1 mode: 16.384, 32.768 or 65.536 mhz t1 mode: 12.352, 24.704 or 49.408 mhz 8khz_ref u2 i 8 khz external reference clock input: lop r4 i loss of power / input pin for messaging transmit encoder liu interface (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 25 rev. 1.0.1 octal t1/e1/j1 framer liu control (framer channel number indicated by _n) s ignal n ame p in # t ype d escription los_0 los_1 los_2 los_3 los_4 los_5 los_6 los_7 g4 j4 k1 m2 v2 aa1 ab3 af1 i loss of signal input?liu interface-framer_n: this input pin is intended to be connected to the rxlos output pin of the liu associated with framer_n. if the liu ic detects an los condition and asserts (toggles "high") this input pin, then the receive framer associated with channel_n will declare a los c ondition. asserting this input pin "high" will result in framer_n asserting the rxlos_n output pin. gpo7 cs1 p1 o general purpose output pin/chip select output pin: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo7 this pin is a general purpose output pin that is controlled by the contents of bit- field 7, within the line control register (address = 00h, 02h). host mode: cs1 this pin is a chip select output pin that is asserted (toggles ?low?) following a write operation to the liu access register 1, associated with framer 4, 5, 6 and 7 . this output pin is intended to be tied to the chip select input of an liu (or other peripheral device) that is configurable via a microprocessor serial inter - face. once the host mode serial port has completed its read or write opera - tion, then it will negate (toggle "high") this output pin. gpo6 sclk1 p2 o general purpose output pin/serial clock output: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo6 this pin is a general purpose output pin that is controlled by the contents of bit- field 6, within the line control register (address = 00h, 02h). host mode:sclk1 this pin functions as the serial clock output signal (sclk), when the liu con - troller block is configured to operate in the host mode gpo5 sdi1 p4 o general purpose output pin/serial data input bit 1: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo5 this pin is a general purpose output pin that is controlled by the contents of bit- field 5, within the line control register (address = 00h, 02h). host mode:sdi1 this pin functions as the serial data input (sdi) output pin (to the microproces - sor serial interface). gpo4 sdo1 r1 o general purpose output pin/serial data output bit 0: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo4 this pin is a general purpose output pin that is controlled by the contents of bit- field 4, within the line control register (address = 00h, 02h). host mode:sdo1 this pin functions as the serial data output (sdo) input pin (into the liu con - troller block).
xrt84l38 26 octal t1/e1/j1 framer rev. 1.0.1 gpo3 cs0 m1 o general purpose output pin/chip select output pin: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo3 this pin is a general purpose output pin that is controlled by the contents of bit- field 3, within the line control register (address = 0x00, 0x02). host mode: cs0 this pin is a chip select output pin that is asserted (toggles ?low?) following a write operation to the liu access register 1, associated with framer 0,1, 2 and 3. this output pin is intended to be tied to the chip select input of an liu (or other peripheral device) that is configurable via a microprocessor serial inter - face. once the host mode serial port has completed its read or write opera - tion, then it will negate (toggle "high") this output pin. gpo2 sclk0 n2 o general purpose output/serial clock output: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo2 this pin is a general purpose output pin that is controlled by the contents of bit- field 2, within the line control register (address = 00h, 02h). host mode: sclk0 this pin functions as the serial clock output signal (sclk), when the liu con - troller block is configured to operate in the host mode. gpo1 sdi0 n3 o general purpose output pin/serial data in output pin: the exact role of this output pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo1 this pin is a general purpose output pin that is controlled by the contents of bit field 1, within the line control register (address = 00h, 02h) host mode: sdi this pin functions as the serial data input (sdi) output pin (to the microproces - sor serial interface). gpo0 sdo0 n1 i or o general purpose output pin/serial data out input pin: the exact role of this pin depends upon whether the liu controller block is operating in the hardware or host mode. hardware mode: gpo0 this pin is a general purpose output pin that is controlled by the contents of bit- field 0, within the line control register (address = 00h, 02h). host mode: sdo0 this input pin functions as the serial data output (sdo) input pin (into the liu controller block). jtag (framer channel number indicated by _n) s ignal n ame p in # t ype d escription tck a1 i test clock: boundary scan clock input. note : this input pin should be pulled ?low? for normal operation tms c2 i test mode select: boundary scan mode select input. note : this input pin should be pulled ?low? for normal operation liu control (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 27 rev. 1.0.1 octal t1/e1/j1 framer tdi b1 i test data in: boundary scan test data input note : this input pin should be pulled ?low? for normal operation tdo d3 o test data out: boundary scan test data output trst c3 i jtag test reset input test mode p3 i factory test mode pin note: user should tie this pin to ground microprocessor interface (framer channel number indicated by _n) s ignal n ame p in # t ype d escription data0 data1 data2 data3 data4 data5 data6 data7 r24 r25 n26 n25 l24 k25 k24 j24 i/o bidirectional microprocessor data bus bit 0--lsb bidirectional microprocessor data bus bit 1 bidirectional microprocessor data bus bit 2 bidirectional microprocessor data bus bit 3 bidirectional microprocessor data bus bit 4 bidirectional microprocessor data bus bit 5 bidirectional microprocessor data bus bit 6 bidirectional microprocessor data bus bit 7--msb req0 req1 t26 u23 o dma cycle request output?dma controller 0 (write) : the framer asserts this output pin (toggles it "low") when at least one of the transmit hdlc buffers are empty and can receive one more hdlc message. the framer negates this output pin (toggles it ?high?) when the hdlc buffer can no longer receive another hdlc message. dma cycle request output?dma controller 1 (read): the framer asserts this output pin (toggles it "low") when one of the receive hdlc buffer contains a complete hdlc message that needs to be read by the c/p. the framer negates this output pin (toggles it high) when the receive hdlc buffers are depleted. int m24 o interrupt request output: the framer will assert this active "low" output (toggles it "low"), to the local p, anytime it requires interrupt service. pclk r23 i microprocessor clock input: this clock signal is the microprocessor interface system clock. this clock signal is used for synchronous/burst/dma data transfer. the maximum frequency of this clock signal is 33mhz. jtag (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 28 octal t1/e1/j1 framer rev. 1.0.1 ptype0 ptype1 ptype2 t25 p24 m25 i microprocessor type input: bit 0 (lsb): this input pin, along with ptype1 and ptype2 permit the user to specify which type of microprocessor/microcontroller to be interfaced the framer. microprocessor type input: bit 1 microprocessor type input: bit 2 rdy_ dtack p23 o ready/data transfer acknowledge output: the exact behavior of this pin depends upon which microprocessor the framer is configured to interface to: intel type microprocessors this output pin toggles "low" when the framer is ready to respond to the current pio (programmed i/o) or burst transaction. motorola type microprocessors this output pin toggles "low" when the framer has completed the current bus cycle. a0 a1 a2 a3 a4 a5 a6 p26 n23 m26 l26 l23 j26 k23 i microprocessor interface address bus input bit 0 -- (lsb) microprocessor interface address bus input bit 1 microprocessor interface address bus input bit 2 microprocessor interface address bus input bit 3 microprocessor interface address bus input bit 4 microprocessor interface address bus input bit 5 microprocessor interface address bus input bit 6 -- (msb) dben p25 i data bus enable input pin . ale_as n24 i address latch enable input_address strobe cs g25 i microprocessor interface?chip select input: the microprocessor/microcontroller must assert this input pin (t oggle it "low") in order to exchange data with the framer. note: for the 68k mpu, this signal is generated by address decode and address strobe. rd r26 i microprocessor interface?read strobe input: the exact behavior of this pin depends upon the type of microprocessor/micro - controller the framer has been configured to interface to, as defined by the ptype[2:0] pins. note: see pin t25 (ptype0) for the p selection table. microprocessor interface (framer channel number indicated by _n) s ignal n ame p in #t ype d escription 0 1 0 1 0 1 ptype0 0 0 1 1 0 0 0 0 0 0 1 1 ptype1 ptype2 68hc11, 8051, 80c188 motorola 68k intel x86 idt3051/52 ibm power pc 403 intel i960 microprocessor type
xrt84l38 29 rev. 1.0.1 octal t1/e1/j1 framer wr g26 i microprocessor interface?write strobe input "low" : indicates current bus cycle is a write cycle: intel 51, 188, mips350x "high" : indicates present bus cycle is a write cycle: intel x86, i960 "low" : indicates current bus cycle is a read cycle: intel x86, i960 "high" : indicates present bus cycle is a read cycle: motorola, power pc 403 "low" : also used as write strobe in dma transfer ack0 ack1 u26 t23 i i dma cycle acknowledge input?dma controller 0 (write): the external dma controller will assert this input pin ?low? when the following two conditions are met: a. after the dma controller, within the framer has asserted (toggled ?low?), the req_0 output signal. b. when the external dma controller is ready to transfer data from external memory to the selected transmit hdlc buffer. at this point, the dma transfer between the external memory and the selected transmit hdlc buffer may begin. after completion of the dma cycle, the external dma controller will negate this input pin after the dma controller within the framer has negated the req_0 out - put pin. the external dma controller must do this in order to acknowledge the end of the dma cycle. dma cycle acknowledge input?dma controller 1 (read): the external dma controller asserts this input pin ?low? when the following two conditions are met: a. after the dma controller, within the framer has asserted (toggled "low"), the req_1 output signal. b. when the external dma controller is ready to transfer data from the selected receive hdlc buffer to external memory. at this point, the dma transfer between the selected receive hdlc buffer and the external memory may begin. after completion of the dma cycle, the external dma controller will negate this input pin after the dma controller within the framer has negated the req_1 out - put pin. the external dma controller will do this in order to acknowledge the end of the dma cycle. blast l25 i last cycle of burst indicator input: the microprocessor asserts this pin ?low?when it is performing its last read or write cycle, within a burst operation. reset r3 i reset input: active "low" microprocessor interface (framer channel number indicated by _n) s ignal n ame p in #t ype d escription
xrt84l38 30 octal t1/e1/j1 framer rev. 1.0.1 power supply pins s ignal n ame p in # t ype d escription vdd l11 l12 l13 l14 l15 l16 m11 m12 m15 m16 n11 n12 n15 n16 r11 r12 r15 r16 **** power supply pins ground pins s ignal n ame p in # t ype d escription gnd m13 m14 n13 n14 p13 p14 r13 r14 t11 t12 t13 t14 t15 t16 **** ground pins
xrt84l38 31 rev. 1.0.1 octal t1/e1/j1 framer no connect pins s ignal n ame p in # t ype d escription nc a6 a20 b7 b17 c12 c13 c16 c23 d14 d17 e1 e2 f4 h25 h26 k26 m23 u3 u4 u25 v3 y4 aa25 ac23 ad26 ae3 ae14 ae15 ae17 ae25 af2 af11 af14 af22 af24 not connected
xrt84l38 32 octal e1/t1/j1 framer rev. 1.0.1 electrical characteristics absolute maximums power supply......................................... - 0.5v to +3.465v power dissipation pbga package........................... 2w storage temperature ...............................-65c to 150c input logic signal voltage (any pin) .........-0.5v to + 5.5v operating temperature range.................-40c to 85c esd protection...................................................>2000v supply voltage ...................... gnd-0.5v to +vdd + 0.5v input current (any pin) ...................................... + 100ma dc electrical characteristics test conditions: ta = 25c, vdd = 3.3v + 5% unless otherwise specified s ymbol p arameter m in . t yp . m ax . u nits c onditions i dd power supply current 450 ma all channels on i ll data bus tri-state bus leakage current -10 +10 a v il input low voltage 0.6 v pdata[0:7] 0.8 v all others v ih input high voltage 2.7 vdd v pdata[0:7] 2.0 vdd v all others v ol output low voltage 0.0 0.4 v i ol = 2ma v oh output high voltage 2.4 vdd v i oh = 2ma i oc open drain output leakage current -10 10 a i ih input high voltage current -10 10 a v ih = vdd input high voltage current (with pull-down resistor) 100 400 i il input low voltage current -10 10 a v il = gnd input low voltage current (with pull-up resistor) -150 -30 t able 2: xrt84l38 p ower c onsumption (vdd=3.3v5%, t a =25c unless otherwise specified) m ode s upply v oltage m in t yp m ax u nit t1 3.3v - 1.8 2.0 w e1 3.3v - 1.5 1.8 w
xrt84l38 33 rev. 1.0.1 octal t1/e1/j1 framer 1.0 microprocessor interface block the microprocessor interface section supports communication between the local microprocessor (p) and the framer. the microprocessor interface supports the following features: ? communicates through a 7 bit address bus (4 bit for one framer) and an 8 bit data bus. ? supports dma read/write data interface ? supports burst transfers ? supports programmed i/o read and write, wait cycle extended with ready/ dtack the microprocessor interface section supports the following operations: ? channel selection ? writing configuration data into the fr amer on-chip (addressable) registers ? writing outbound pmdl (path maintenance data link) messages into the transmit lapd message buffer of the framer ? generation of interrupt requests to the p ? servicing interrupt requests from the framer ? monitoring the system's health by periodically reading the on-chip performance monitor registers ? reading inbound pmdl messages from the receive lapd message buffer of the framer each of these operations (between the local microprocessor and the framer ic) is discussed in detail, throughout this data sheet. the framer supports the following microprocessors/microcontrollers with a minimum amount of glue logic. ? intel 8051, 80c188, x86, i960 ? motorola 68hc11, 68k ? mips 3051/52 ? powerpc 403 the type of microprocessor/microcontroller to interface to the framer is specified by tying the ptype[2:0] pins to the appropriate level. table 1, lists the values for ptype[2:0] and the corresponding p/c types. the behavior of some of the pins, associated with the microprocessor interface, depends upon the value that the user has applied to the ptype[2:0] input pins. the next sections present a detailed discussion on the role of each of these pins, and how to configure the framer to interface to each of these types of microprocessors. the framer connects to the microcontroller as if it were external memory. the microcontroller can read or write to two different storage elements in the framer: t able 3: c/ p s election t able ptype[2:0] i nput l evels c orresponding c/ p 000 68hc11, 8051, 80c188 001 motorola 68000 family 010 intel x86 family 011 intel i960 100 idt3051/52 (mips) 101 ibm powerpc 403
xrt84l38 34 octal t1/e1/j1 framer rev. 1.0.1 ? flip-flop types of registers ? rams the configuration of the framer, including the enabling/disabling of interrupts, is selected by setting values in various control registers. the registers can be read as well as written. the framer can be designed into both polled and interrupt-driven systems. all detection of change of state of alarm conditions, data link events, error events, or counter overflows can be programmed to cause interrupts. the microcontroller interface block within the framer supports three types of data transfer schemes: ? programmable input/output (pio) ? burst transfer ? dma (direct memory access) each of these data transfer methods are also discussed in the next sections. 1.1 channel selection within the framer the xrt84l38 framer consists of eight independent banks of configuration registers. each of these banks are identical and correspond to each of the eight channels within the xrt84l38. the xrt84l38 permits selection of and access to, any one of these configuration register banks, via the three (3) most significant address pins, a4, a5 and a6. the relationship between the states of a4, a5 and a6, and the corresponding configuration register bank, is shown below. t able 4: c hannel s election a6 a5 a4 c onfiguration r egister b ank 0 0 0 channel 0 0 0 1 channel 1 0 1 0 channel 2 0 1 1 channel 3 1 0 0 channel 4 1 0 1 channel 5 1 1 0 channel 6 1 1 1 channel 7
xrt84l38 35 rev. 1.0.1 octal t1/e1/j1 framer 1.2 the microprocessor interface block signal the framer may be configured into different operating modes and have its performance monitored by software through a standard microprocessor, using data, address and control signals. the local p configures the framer (into a desired operating mode) by writing data into specific addressable, on-chip read/write registers, or on-chip ram. the mi croprocessor interface provides the signals which are required for a general purpose microprocessor to read or write data into these registers. the microprocessor interface also supports polled and interrupt driven environments. these interface signals are described below in table 5 , table 6 , and table 7 . the microprocessor interface can be configured to operate in the motorola mode, the intel mode, as well as other modes. when the microprocessor interface is operating in the motorola mode, some of the control signals function in a manner required by the motorola 68000 family of microprocessors. likewise, when the microprocessor interface is operating in the intel mode, then these control signals function in a manner as required by the intel 80xx family of microprocessors. table 5 lists and describes those microprocessor interface signals whose role is constant across the two modes. table 6 describes the role of some of these signals when the microprocessor interface is operating in the intel mode . likewise, table 7 describes the role of these signals when the microprocessor interface is operating in the motorola mode . f igure 3. s implified b lock d iagram of the m icroprocessor i nterface b lock t able 5: xrt84l38 m icroprocessor i nterface s ignals that exhibit constant roles in both the i ntel and m otorola m odes p in n ame t ype d escription ptype[2:0] i microprocessor interface mode select input pins these three pins are used to specify the microprocessor mode that the microprocessor inter - face will operate in. the relationship betw een the state of these three input pins, and the cor - responding microprocessor mode is presented in table 1. d[7:0] i/o bi-directional data bus for register read or write operations. microprocessor interface & programmable registers dma interface wr rd ale_as blast ptype [2:0] rdy/dtack reset dben clk cs int a[6:0] data[7:0] ack[1:0] req[1:0]
xrt84l38 36 octal t1/e1/j1 framer rev. 1.0.1 1.3 interfacing the xrt84l38 to the local c/p via the microprocessor interface block a[6:0] i seven-bit address bus inputs the xrt84l38 framer microprocessor interface uses a multiplexed address bus. this address bus is provided to permit the user to select an on-chip register or buffer location for read/write access. cs i chip select input this active-low signal selects the microprocessor interface of the xrt84l38 framer and enables read/write operations with the on-chip registers/buffer locations. t able 6: i ntel mode : m icroprocessor i nterface s ignals xrt84l38 p in n ame i ntel e quivalent p in t ype d escription ale_as ale i address-latch enable: this active-high signal is used to latch the contents on the address bus, a[6:0]. the contents of the address bus are latched into the a[6:0] inputs on the falling edge of ale_as. additionally, this signal can be used to indicate the start of a burst cycle. rd rd* i read signal: this active-low input functions as the read signal from the local p . when this signal goes "low", the framer microprocessor interface places the contents of the addressed register on the data bus pins, d[7:0]. the data bus is tri-stated once this input signal returns "high". wr wr* i write signal: this active-low input functions as the write signal from the local p . the contents of the data bus (d[7:0]) is written into the addressed register via a[6:0], on the rising edge of this signal. rdy_ dtac k ready* o ready output: this active-low signal is provided by the framer and indicates that the current read or write cycle is to be extended until this signal is asserted. the local p typically inserts wait states until this signal is asserted. this output toggles "low" when the device is ready for the next read or write cycle. t able 7: m otorola m ode : m icroprocessor i nterface s ignals xrt84l38 p in n ame m otorola e quivalent p in t ype d escription ale_as as* i address strobe: this active-low signal is used to latch the contents on the address bus input pins, a[6:0], into the microprocessor interface circuitry. the contents of the address bus are latched into the framer on the rising edge of the ale_as signal. this signal can also be used to indicate the start of a burst cycle. rd ds* i data strobe: this signal latches the contents of the bi-directional data bus pins into the addressed register within the framer during a write cycle. wr r/w* i read/write input: when this pin is "high", it indicates a read cycle. when this pin is "low", it indicates a write cycle. rdy_ dtac k dtack* o data transfer acknowledge: the framer asserts dtack in order to inform the cpu that the present read or write cycle is nearly complete. the 68000 fam - ily of cpus requires this signal from its peripheral devices in order to quickly and properly complete a read or write cycle. t able 5: xrt84l38 m icroprocessor i nterface s ignals that exhibit constant roles in both the i ntel and m otorola m odes p in n ame t ype d escription
xrt84l38 37 rev. 1.0.1 octal t1/e1/j1 framer the microprocessor interface block within the framer is very flexible and provides the following options: ? interface the framer to a c/p over an 8-bit wide bi-directional data bus. ? interface the framer to an intel-type or motorola-type c/p. ? transfer data (between the framer ic and the c/p) via the programmed i/o or burst mode 1.3.1 interfacing the framer to the microprocessor over an 8 bit wide bi-directional data bus the framer microprocessor interface permits the user to interface it to a c/p over an 8-bit wide bi-directional data bus. in general, interfacing the framer to an 8-bit c/p is quite straight-forward. this is because most of the registers, within the framer, are 8-bits wide. in this mode, the c/p can read or write data into both even and odd numbered addresses within the framer address space. example: consider that an 8-bit c/p needs to read in the pmon lcv event count register. in order to accomplish this task, the 8-bit c/p needs to read in the contents of pmon lcv event count register - msb (located at address = 0x50) and the contents of the pmon lcv event count register - lsb (located at address = 0x51). these two eight-bit registers when concatenated together make up the pmon lcv event count register. if the 8-bit c/p reads in the pmon lcv event count-lsb register first, then the entire pmon lcv event count register will be reset to 0x0000. as a consequence, if the 8-bit c/p attempts to read in the pmon lcv event count-msb register in the very next read cycle, it will read in the value 0x00. 1.3.2 data access modes the microprocessor interface block supports data transfer between the framer and the c/p (e.g., read and write operations) via the programmed i/o and the burst modes. 1.3.2.1 programmed i/o programmed i/o is basically a handshaking type of asynchronous bus access, which provides relatively slow single read and write data transfers. the microprocessor must supply an address value to the address bus input pins a[6:0] with each read and write cycle. because of the indirect addressing scheme each pio reads and write access requires two accesses, as illustrated below. in the first access, the microprocessor is specifying two things: 1. which of the four framer register sets it intends to access. 2. which group of registers within the selected framer?s register sets, the microprocessor wants to access. as a slave, the e1 is the target of access generated by a bus master, the cpu. slave accesses are accepted by the slave control state machine, then passed to related functional logic. address is buffered and decoded to address relevant destination. data is also latch in both write and read directions. pio operations are e nabled by the chip select (cs) input signal. framer pio interface supports pipelined (buffered) writes to increase bus throughput. all internal registers and accessible memory are addressable through 6 bits of address bus. 1.3.2.2 data access using programmed i/o programmed i/o is the conventional manner in which a microprocessor exchanges data with a peripheral device. however, it is also the slowest method of data exchange between the framer and the c/p. 1.3.2.2.1 intel mode programmed i/o access if the framer is interfaced to an intel-type c/p (e.g., the 80x86 family, etc.), then it should be configured to operate in the intel mode. 1.3.2.2.1.1 intel mode read cycle whenever an intel-type c/p wishes to read the contents of a register or some location within the receive lapd message buffer or the receive oam cell buffer, within the framer, it should do the following. 1. place the address of the target register or buffer location, within the framer, on the address bus input pins a[6:0].
xrt84l38 38 octal t1/e1/j1 framer rev. 1.0.1 2. while the c/p is placing this address value on the address bus, the address decoding circuitry within the user's system should assert the cs (chip select) pin of the framer, by toggling it "low". this action enables further communication between the c/p and the framer microprocessor interface block. 3. toggle the ale_as (address latch enable) input pin "high". this step enables the address bus input driv - ers, within the microprocessor interface block of the framer. 4. after allowing the data on the address bus pins to settle, by waiting the appropriate address data setup time, the c/p should toggle the ale_as pin "low". this step causes the framer to latch the contents of the address bus into its internal circuitry. at this point, the address of the register or buffer locations, within the framer, has been selected. 5. next, the c/p should indicate that this current bus cycle is a read operation by toggling the rd _ds (read strobe) input pin "low". this action also enables the bi-directional data bus output drivers of the framer. at this point, the bi-directional data bus output drivers proceeds to drive the contents of the latched addressed register, or buffer location, onto the bi-directional data bus, d[7:0]. 6. immediately after the c/p toggles the read strobe signal "low", the framer toggles the rdy_ dtack output pin "low". the framer does this in order to inform the c/p that the data to be read from the data bus is not ready to be latched into the c/p. 7. after some settling time, the data on the bi-directional data bus stabilizes and can be read by the c/p. the framer indicates that this data can be read by toggling the rdy_ dtack (ready) signal "high". 8. after the c/p detects the rdy_ dtack signal, from the framer, it can terminate the read cycle by tog - gling the rd _ds (read strobe) input pin "high". figure 4 presents a timing diagram which illustrates the behavior of the microprocessor interface signals during an intel-type programmed i/o read operation. 1.3.2.2.1.2 the intel mode write cycle whenever an intel-type c/p wishes to write a byte or word of data into a register or buffer location, within the framer, it should do the following. 1. assert the ale_as (address latch enable) input pin by toggling it "high". when the c/p asserts the ale_as input pin, it enables the address bus input drivers within the framer chip. 2. place the address of the target register or buffer location, within the framer, on the address bus input pins, a[6:0]. 3. while the c/p is placing this address value onto the address bus, the address decoding circuitry within the user's system should assert the cs input pin of the framer by toggling it "low". this step enables fur - ther communication between the c/p and the framer microprocessor interface block. f igure 4. i ntel p i nterface signals during p rogrammed i/o r ead o peration ale_as a[6:0] cs d[7:0] rd wr_r/w rdy_dtack not valid valid address of target register
xrt84l38 39 rev. 1.0.1 octal t1/e1/j1 framer 4. after allowing the data on the address bus pins to settle, by waiting the appropriate address setup time, the c/p should toggle the ale_as input pin "low". this step causes the framer to latch the contents of the address bus into its internal circuitry. at this point, the address of the register or buffer location within the framer, has been selected. 5. next, the c/p should indicate that this current bus cycle is a write operation by toggling the wr _r/ w (write strobe) input pin "low". this action also enables the bi-directional data bus input drivers of the framer. 6. the c/p should then place the byte or word that it intends to write into the target register on the bi-direc - tional data bus, d[7:0]. 7. after waiting the appropriate amount of time for the data on the bi-directional data bus to settle, the c/p should toggle the wr _r/ w (write strobe) input pin "high". this action accomplishes two things: a. it latches the contents of the bi-directional data bus into the framer microprocessor interface block. b. it terminates the write cycle. figure 5 presents a timing diagram which illustrates the behavior of the microprocessor interface signals, during an intel-type programmed i/o write operation. 1.3.2.2.2 motorola mode programmed i/o access if the framer is interfaced to a motorola-type c/p (e.g., the mc680x0 family, etc.), it should be configured to operate in the motorola mode. 1.3.2.2.2.1 motorola mode read cycle whenever a motorola-type c/p wishes to read the contents of a register or some location within the receive lapd message or receive oam cell buffer, within the framer, it should do the following. 1. assert the ale_as (address-strobe) input pin by toggling it ?low?. this step enables the address bus input drivers within the microprocessor interface block of the framer. 2. place the address of the target register or buffer location within the framer, on the address bus input pins, a[6:0]. 3. at the same time, the address decoding circuitry within the user's system should assert the cs (chip select) input pin of the framer, by toggling it "low". this action enables further communication between the c/p and the framer microprocessor interface block. 4. after allowing the data on the address bus pins to settle, by waiting the appropriate address setup time, the c/p should toggle the ale_as input pin "high". this step causes the framer to latch the contents of the address bus into its internal circuitry. at this point, the address of the register or buffer location within the framer has been selected. f igure 5. i ntel p i nterface s ignals during p rogrammed i/o w rite o peration ale_as a[6:0] cs d[7:0] rd wr_r/w rdy_dtack data to be written address of target register
xrt84l38 40 octal t1/e1/j1 framer rev. 1.0.1 5. further, the c/p should indicate that this cycle is a read cycle by setting the wr _r/ w (r/w*) input pin "high". 6. next the c/p should initiate the current bus cycle by toggling the rd _ds (data strobe) input pin "low". this step enables the bi-directional data bus output drivers, within the framer. at this point, the bi-direc - tional data bus output drivers will proceed to drive the contents of the address register onto the bi-direc - tional data bus, d[7:0]. 7. after some settling time, the data on the bi-directional data bus will stabilize and can be read by the c/p. the framer will indicate that this data can be read by asserting the rdy_ dtack (dtack) signal ?low?. 8. after the c/p detects the rdy_ dtack signal (from the framer) it will terminate the read cycle by tog - gling the rd _ds (data strobe) input pin "high". figure 6 presents a timing diagram which illustrates the behavior of the microprocessor interface signals during a motorola-type programmed i/o read operation. 1.3.2.2.2.2 motorola mode write cycle whenever a motorola-type c/p wishes to write a byte or word of data into a register or buffer location, within the framer, it should do the following. 1. assert the ale_as (address select) input pin by toggling it "low". this step enables the address bus input drivers (within the framer chip). 2. place the address of the target register or buffer location (within the framer), on the address bus input pins, a[6:0]. 3. while the c/p is placing this address value onto the address bus, the address-decoding circuitry (within the user's system) should assert the cs (chip select) input pins of the framer by toggling it "low". this step enables further communication between the c/p and the framer microprocessor interface block. 4. after allowing the data on the address bus pins to settle (by waiting the appropriate address setup time), the c/p should toggle the ale_as input pin "high". this step causes the framer to latch the contents of the address bus into its own circuitry. at this point, the address of the register or buffer location (within the framer), has now been selected. 5. further, the c/p should indicate that this current bus cycle is a write operation by toggling the wr _r/ w (r/w*) input pin "low". 6. the c/p should then place the byte or word that it intends to write into the target register, on the bi-direc - tional data bus, d[7:0]. f igure 6. m otorola p i nterface signals during a p rogrammed i/o r ead o peration ale_as a[6:0] cs d[7:0] rd_ds wr_r/w rdy_dtack not valid address of target register valid data
xrt84l38 41 rev. 1.0.1 octal t1/e1/j1 framer 7. next, the c/p should initiate the bus cycle by toggling the rd _ds (data strobe) input pin "low". when the framer senses that the wr _r/ w (r/w*) input pin is "high" and that the rd _ds (data strobe) input pin has toggled "low", it will enable the input drivers of the bi-directional data bus, d[7:0]. 8. after waiting the appropriate time, for this newly placed data to settle on the bi-directional data bus (e.g., the data setup time) the framer will assert the rdy_ dtack output signal ?low?. 9. after the c/p detects the rdy_ dtack signal (from the framer), the c/p should toggle the rd _ds input pin "high". this action accomplishes two things. a. it latches the contents of the bi-directional data bus into the microprocessor interface block. b. it terminates the write cycle. figure 7 presents a timing diagram which illustrates the behavior of the microprocessor interface signals, during a motorola-type programmed i/o write operation. 1.3.2.3 burst mode i/o for data access burst mode i/o access is a much faster way to transfer data between the c/p and the microprocessor interface (of the framer), than programmed i/o. the reason why burst mode i/o is faster is explained below. data is placed upon the address bus input pins a[6:0] only for the very first access, within a given burst access. the remaining read or write operations (within this burst access) do not require the placement of the address data on the address data bus. as a consequence, the user does not have to wait through the address setup and hold times for each of these read/write operation, within the burst access. it is important to note that there are some limitations associated with burst mode i/o operations. 1. all cycles within the burst access, must be either all read or all write cycles. no mixing of read and write cycles is permitted. 2. a burst access can only be used when read or write operations are to be employed over a contiguous range of address locations, within the framer. 3. the very first read or write cycle, within a burst access, must start at the lowest address value, of the range of addresses to be accessed. subsequent operations will automatically be incremented to the very next higher address value. examples of burst mode i/o operations are presented below for read and write operations, with both intel-type and motorola-type c/p. 1.3.2.3.1 burst i/o access: intel mode f igure 7. m otorola p i nterface signal during p rogrammed i/o w rite o peration ale_as a[6:0] cs d[7:0] rd wr rdy_dtack data to be written address of target register
xrt84l38 42 octal t1/e1/j1 framer rev. 1.0.1 if the xrt84l38 framer is interfaced to an intel-type c/p (e.g., the 80x86 family, etc.), then it should be configured to operate in the intel mode (by tying the moto pin to ground). intel-type read and write burst i/o access operations are described below. 1.3.2.3.1.1 intel-mode read burst access when an intel-type c/p wants to read the contents of numerous registers or buffer locations over a contiguous range of addresses, then it should do the following. a. perform the initial read operation of the burst access. b. perform the remaining read operations of the burst access. c. terminate the burst access operation. each of these operations within the burst access are described below. 1.3.2.3.1.1.1 initial read operation: intel mode the initial read operation of an intel-type read burst access is accomplished by executing a programmed i/o read cycle as summarized below. a.0 execute a single ordinary (programmed i/o) read cycle, as described in steps a.1 through a.7 below. a.1 place the address of the initial-target register or buffer location (within the framer) on the address bus input pins a[6:0]. a.2 while the c/p is placing this address value onto the address bus, the address decoding circuitry (within the user's system) should assert the cs input pin of the framer, by toggling it "low". this step enables further communication between the c/p and the framer microprocessor interface block. a.3 assert the ale_as (address latch enable) pin by toggling it "high". this step enables the address bus input drivers, within the microprocessor interface block of the framer. a.4 after allowing the data on the address bus pins to settle (by waiting the appropriate address data setup time), the c/p should then toggle the ale_as pin "low". this step latches the contents, on the address bus pins, a[6:0], into the framer microprocessor interface block. at this point, the initial address of the burst access has now been selected. n ote : the ale_as input pin should remain "low" for the remainder of this burst access operation. a.5 next, the c/p should indicate that this current bus cycle is a read operation by toggling the rd _ds (read strobe) input pin "low". this action also enables the bi-directional data bus output drivers of the framer. at this point, the bi-directional data bus output drivers will proceed to drive the contents of the addressed register onto the bi-directional data bus, d[7:0]. a.6 immediately after the c/p toggles the read strobe signal "low", the framer will toggle the rdy_ dtack (ready) output pin "low". the framer does this in order to inform the c/p that the data (to be read from the data bus) is not ready to be latched into the c/p. a.7 after some settling time, the data on the bi-directional data bus will stabilize and can be read by the c/p. the framer will indicate that this data is ready to be read, by toggling the rdy_ dtack (ready) signal "high". a.8 after the c/p detects the rdy_ dtack signal (from the framer), it can then will terminate the read cycle by toggling the rd _ds (read strobe) input pin "high".
xrt84l38 43 rev. 1.0.1 octal t1/e1/j1 framer figure 8 presents an illustration of the behavior of the microprocessor interface signals, during the initial read operation, within a burst i/o cycle for an intel-type c/p. at the completion of this initial read cycle, the c/p has read in the contents of the first register or buffer location (within the framer) for this particular burst i/o access operation. in order to illustrate how this burst access operation works, the byte (or word) of data, that is being read in figure 8 , has been labeled valid data at offset = 0x00. this label indicates that the c/p is reading the very first register (or buffer location) in this burst access operation. f igure 8. i ntel p i nterface s ignals , during the i nitial r ead o peration of a b urst c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr not valid address of initial target register (offset = 0x00) valid data of offset = 0x00
xrt84l38 44 octal t1/e1/j1 framer rev. 1.0.1 1.3.2.3.1.1.2 subsequent read operations the procedure that the c/p must use to perform the remaining read cycles, within this burst access operation, is presented below. b.0 execute each subsequent read cycles, as described in steps 1 through 3 below. b.1 without toggling the ale_as input pin (e.g., keeping it "low"), toggle the rd _ds input pin "low". this step accomplishes the following. a. the framer will internally increments the latched address value (within the microprocessor interface circuitry). b. the output drivers of the bi-directional data bus, d[7:0] are enabled. at some time later, the register or buffer location corresponding to the incremented latched address value will be driven onto the bi-directional data bus. b.2 immediately after the read strobe pin toggles "low" the framer will toggle the rdy_ dtack (ready) output pin "low" to indicate its not ready status. b.3 after some settling time, the data on the bi-directional data bus will stabilize and can be read by the c/p. the framer will indicate that this data is ready to be read by toggling the rdy_ dtack (ready) signal "high". b.4 after the c/p detects the rdy_ dtack signal (from the framer), it can terminate th e read cycle by toggling the rd _ds (read strobe) input pin "high". for subsequent read oper ations, within this burst cycle, the c/p simply repeats steps 1 through 3, as illustrated in figure 9 . in addition to the behavior of the microprocessor interface signals, figure 9 also illustrates other points regarding the burst access operation. a. the framer internally increments the address value, from the original latched value shown in figure 8 . this is illustrated by the data, appearing on the data bus, (for the first read access) being labeled valid data at offset = 0x01 and that for the second read access being labeled valid data at offset = 0x02. b. the framer performs this address incrementing process even though there are no changes in the address bus data, a[6:0]. f igure 9. i ntel p i nterface s ignals , during subsequent r ead o perations of a b urst i/o c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr not valid valid data at offset = 0x01 not valid valid data at offset = 0x02 address of initial target register (offset = 0x00)
xrt84l38 45 rev. 1.0.1 octal t1/e1/j1 framer 1.3.2.3.1.1.3 terminating the burst access operation the burst access operation will be terminated upon the rising edge of the ale_as input signal. at this point the framer will cease to internally increment the latched address value. further, the c/p is now free to execute either a programmed i/o access or to start another burst access operation with the framer. 1.3.2.3.1.2 write burst access: intel-mode when an intel-type c/p wishes to write data into a contiguous range of addresses, then it should do the following. a. perform the initial write operation of the burst access. b. perform the remaining write operations, of the burst access. c. terminate the burst access operation. each of these operations within the burst access are described below. 1.3.2.3.1.2.1 initial write operation the initial write operation of an intel-type write burst access is accomplished by executing a programmed i/o write cycle as summarized below. a.0 execute a single ordinary (programmed i/o) writ e cycle, as described in steps a.1 through a.7 below. a.1 place the address of the initial target register (or buffer location) within the framer, on the address bus pins, a[6:0]. a.2 at the same time, the address-decoding circui try (within the user's system) should assert the cs (chip select) input pin of the framer, by toggling it "low". this step enables further communication between the c/p and the framer microprocessor interface block. a.3 assert the ale_as (address latch enable) input pin "high". this step enables the address bus input drivers, within the microprocessor interface block of the framer. a.4 after allowing the data on the address bus pins to settle (by waiting the appropriate address setup time), the c/p should then toggle the ale_as input pin "low". this step latches the contents, on the address bus pins, a[6:0], into the xrt84l38 framer microprocessor interface block. at this point, the initial address of the burst access has now been selected. n ote : the ale_as input pin should remain "low" for the remainder of this burst i/o access operation. a.5 next, the c/p should indicate that this current bus cycle is a write operation by keeping the rd _ds pin "high" and toggling the wr _r/ w (write strobe) pin "low". this action also enables the bi- directional data bus input drivers of the framer. a.6 the c/p places the byte (or word) that it intends to write into the target register on the bi-directional data bus, d[7:0]. a.7 after waiting the appropriate amount of time, for the data (on the bi-directional data bus) to settle, the c/p should toggle the wr _r/ w (write strobe) input pin "high". this action accomplishes two things. a. it latches the contents of the bi-directional data bus into the framer microprocessor interface block. b. it terminates the write cycle.
xrt84l38 46 octal t1/e1/j1 framer rev. 1.0.1 figure 10 presents a timing diagram which illustrates the behavior of the microprocessor interface signals, during the initial write operation within a burst access, for an intel-type c/p. at the completion of this initial write cycle, the c/p has written a byte or word into the first register or buffer location (within the framer) for this particular burst access operation. in order to illustrate this point, the byte (or word) of data, that is being written in figure 10 has been labeled data to be written (offset = 0x00). f igure 10. i ntel p i nterface signals , during the i nitial w rite o peration of a b urst c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr address of initial target register (offset = 0x00) data to be written (offset = 0x00)
xrt84l38 47 rev. 1.0.1 octal t1/e1/j1 framer 1.3.2.3.1.2.2 the subsequent write operations the procedure that the c/p must use to perform the remaining write cycles, within this burst access operation, is presented below. b.0 execute each subsequent writ e cycle, as described in steps b.1 through b.3. b.1 without toggling the ale_as input pin (e.g., keeping it "low"), apply the value of the next byte or word (to be written into the framer) to the bi-directional data bus pins, d[7:0]. b.2 toggle the wr _r/ w (write strobe) input pin "low". this step accomplishes two things. a. it enables the input drivers of the bi-directional data bus. b. it causes the framer to internally increment the value of the latched address. b.3 after waiting the appropriate amount of settling time the data, in the internal data bus, will stabilize and is ready to be latched into the framer microprocessor interface block. at this point, the c/p should latch the data into the framer by toggling the wr _r/ w input pin "high". for subsequent write operations, within this burst i/o access, the c/p simply repeats steps b.1 through b.3, as illustrated in figure 11 . 1.3.2.3.1.2.3 terminating the burst i/o access burst access operation will be terminated upon the rising edge of the ale_as input signal. at this point the framer will cease to internally increment the latched address value. further, the c/p is now free to execute either a programmed i/o access or to start another burst access operation with the xrt84l38 framer. 1.3.2.3.2 burst i/o access: motorola mode if the xrt84l38 framer is interfaced to a motorola-type c/p (e.g., the mc680x0 family, etc.), then it should be configured to operate in the motorola mode (by tying the moto pin to vcc). motorola-type read and write burst i/o access operations are described below. 1.3.2.3.2.1 read burst i/o access operation: motorola-mode whenever a motorola-type c/p wishes to read the contents of numerous registers or buffer locations over a contiguous range of addresses, then it should do the following. a. perform the initial read operation of the burst access. b. perform the remaining read operations in the burst access. c. terminate the burst access operation. each of these operations, within the burst access are discussed below. f igure 11. p i nterface s ignals , during subsequent w rite o perations of a b urst i/o c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr address of initial target register (offset = 0x00) data written at offset = 0x01 data written at offset = 0x02
xrt84l38 48 octal t1/e1/j1 framer rev. 1.0.1 1.3.2.3.2.1.1 initial read operation: motorola mode the initial read operation of a motorola-type read burst access is accomplished by executing a programmed i/ o read cycle, as summarized below. a.0 execute a single ordinary (programmed i/o) read cycle, as described in steps a.1 through a.8 below. a.1 assert the ale_as ( as ) input pin by toggling it "low". this step enables the address bus input drivers (within the framer) within the framer microprocessor interface block. a.2 place the address of the initial target register or buffer location (within the framer), on the address bus input pins, a[6:0]. a.3 at the same time, the address-decoding circui try (within the user's system) should assert the cs (chip select) input pins of the framer by toggling it "low". this action enables further communication between the c/p and the framer microprocessor interface block. a.4 after allowing the data on the address bus pins to settle (by waiting the appropriate address setup time), the c/p should toggle the ale_as input pin "high". this step causes the framer to latch the contents of the address bus into its internal circuitry. at this point, the initial address of the burst access has now been selected. a.5 further, the c/p should indicate that th is cycle is a read cycle by setting the wr _r/ w (r/ w ) input pin "high". a.6 next the c/p should initiate the current bus cycle by toggling the rd _ds (data strobe) input pin "low". this step will enable the bi-directional data bus output drivers, within the framer. at this point, the bi-directional data bus output drivers will proceed to driver the contents of the address register onto the bi-directional data bus. a.7 after some settling time, the data on the bi-directional data bus will stabilize and can be read by the c/p. the framer will indicate that this data can be read by asserting the rdy_ dtack (dtack) signal ?low?. a.8 after the c/p detects the rdy_ dtack signal (from the framer) it will terminate the read cycle by toggling the rd _ds (data strobe) input pin "high". figure 12 presents an illustration of the behavior of the microprocessor interface signals during the initial read operation, within a burst i/o cycle, for a motorola-type c/p. f igure 12. m otorola p i nterface s ignals during the i nitial r ead o peration of a b urst c ycle ale_as a[6:0] cs d[7:0] rd wr rdy_dtack not valid address of initial target register (offset = 0x00) valid data at offset = 0x00
xrt84l38 49 rev. 1.0.1 octal t1/e1/j1 framer at the completion of this initial read cycle, the c/p has read in the contents of the first register or buffer location (within the framer) for this particular burst access operation. in order to illustrate how this burst i/o cycle works, the byte (or word) of data, that is being read in figure 12 has been labeled valid data at offset = 0x00. this indicates that the c/p is reading the very first register (or buffer location) in this burst access. 1.3.2.3.2.1.2 subsequent read operations the procedure that the c/p must use to perform the remaining read cycles, within this burst access operation, is presented below. b.0 execute each subsequent read cycle, as described in steps b.1 through b.3, below. b.1 without toggling the ale_as input pin (e.g., keeping it "high"), toggle the rd _ds (data strobe) input pin "low". this step accomplishes the following. a. the framer internally increments the latched address value (within the microprocessor interface circuitry). b. the output drivers of the bi-directional data bus (d[7:0]) are enabled. at some time later, the register or buffer location corresponding to the incremented latched address value will be driven onto the bi-direc - tional data bus. n ote : in order to insure that the framer will interpret this signal as being a read signal, the c/p should keep the wr _r/ w input pin "high". b.2 after some settling time, the data on the bi-directional data bus will stabilize and can be read by the c/p. the framer will indicate that this data is ready to be read by asserting the rdy_ dtack (dtack) signal ?low?. b.3 after the c/p detects the rdy_ dtack signal (from the framer), it terminates t he read cycl e by toggling the rd _ds (data strobe) input pin "high". for subsequent read operations, within this burst cycle, the c/p simply repeats steps b.1 through b.3, as illustrated in figure 13 . 1.3.2.3.2.1.3 terminating burst access operation the burst i/o access will be terminated upon the falling edge of the ale_as input signal. at this point the framer will cease to internally increment the latched address value. further, the c/p is now free to execute either a programmed i/o access or to start another burst access operation with the framer. 1.3.2.3.2.2 write burst access: motorola-mode whenever a motorola-type c/p wishes to write the contents of numerous registers or buffer locations over a contiguous range of addresses, then it should do the following. f igure 13. m otorola p i nterface s ignals , during subsequent r ead o perations of a b urst i/o c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr not valid address of initial target register (offset = 0x00) valid data at offset = 0x01 not valid valid data at offset = 0x02
xrt84l38 50 octal t1/e1/j1 framer rev. 1.0.1 a. perform the initial write operation of the burst access. b. perform the remaining write operations, of the burst access. c. terminate the burst access operation. 1.3.2.3.2.2.1 initial write operation the initial write operation of a motorola-type write burst access is accomplished by executing a programmed i/o write cycle as summarized below. a.0 execute a single ordinary (programmed i/o) writ e cycle, as described in steps a.1 through a.7 below. a.1 assert the ale_as (address strobe) input pin by toggling it "low". this step enables the address bus input drivers (within the framer). a.2 place the address of the initial target register or buffer location (within the framer), on the address bus input pins, a[6:0]. a.3 at the same time, the address-decoding circuitry (within the user's system) should assert the cs input pin of the framer by toggling it "low". this step enables further communication between the c/p and the framer microprocessor interface block. a.4 after allowing the data on the address bus pins to settle (by waiting the appropriate address setup time), the c/p should toggle the ale_as input pin "high". this step causes the framer to latch the contents of the address bus into its own circuitry. at this point, the initial address of the burst access has now been selected. a.5 further, the c/p should indicate that this current bus cycle is a write operation by toggling the wr _r/ w (r/ w ) input pin "low". a.6 the c/p should then place the byte or word that it intends to write into the target register, on the bi- directional data bus, d[7:0]. a.7 next, the c/p should initiate the bus cycle by toggling the rd _ds (data strobe) input pin "low". when the xrt84l38 framer senses that the wr _r/ w input pin is "low", and that the rd _ds input pin has toggled "low" it will enable the input drivers of the bi-directional data bus, d[7:0]. a.8 after waiting the appropriate amount of time, for this newly placed data to settle on the bi-directional data bus (e.g., the data setup time) the framer will assert the rdy_ dtack (dtack) output signal. a.9 after the p/c detects the rdy_ dtack signal (from the framer) it should toggle the rd _ds input pin "high". this action accomplishes two things: a. it latches the contents of the bi-directional data bus into the framer microprocessor interface block. b. it terminates the write cycle.
xrt84l38 51 rev. 1.0.1 octal t1/e1/j1 framer figure 14 presents a timing diagram which illustrates the behavior of the microprocessor interface signals, during the initial write operation within a burst access, for a motorola-type c/p. at the completion of this initial write cycle, the c/p has written a byte or word into the first register or buffer location (within the framer) for this particular burst i/o access. in order to illustrate how this burst i/o cycle works, the byte (or word) of data, that is being written in figure 14 has been labeled data to be written (offset = 0x00). 1.3.2.3.2.2.2 the subsequent write operations the procedure that the c/p must use to perform the remaining write cycles, within this burst access operation, is presented below. b.0 execute each subsequent write cycle, as described in steps b.1 through b.3. b.1 without toggling the ale_as input pin (e.g., keeping it "low"), apply the value of the next byte or word (to be written into the framer) to the bi-directional data bus pins, d[7:0]. b.2 toggle the wr _r/ w (write strobe) input pin "low". this step accomplishes two things. a. it enables the input drivers of the bi-directional data bus. b. it causes the framer to internally increment the value of the latched address. b.3 after waiting the appropriate amount of settling time the data, in the internal data bus, will stabilize and is ready to be latched into the framer microprocessor interface block. at this point, the c/p should latch the data into the framer by toggling the wr _r/ w input pin "high". f igure 14. m otorola p i nterface signals , during the i nitial w rite o peration of a b urst c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr data to be written (offset = 0x00) address of initial target register (offset = 0x00)
xrt84l38 52 octal t1/e1/j1 framer rev. 1.0.1 for subsequent write operations, within this burst i/o access, the c/p simply repeats steps b.1 through b.3, as illustrated in figure 15 . 1.3.2.3.2.2.3 terminating the burst i/o access the burst i/o access will be terminated upon the falling edge of the ale_as input signal. at this point the framer will cease to internally increment the latched address value. further, the c/p is now free to execute either a programmed i/o access or to start another burst i/o access with the framer. 1.4 dma read/write operations the xrt84l38 framer contains two dma controller interfaces which provide support for all eight framers within the chip. the purpose of the two dma controllers is to facilitate the rapid block transfer of data between an external memory location and the on-chip hdlc buffers via the microprocessor interface. f igure 15. m otorola p i nterface s ignals during subsequent w rite o perations of a b urst i/o c ycle rdy_dtack ale_as a[6:0] cs d[7:0] rd wr address of initial target register (offset = 0x00) data written at offset = 0x01 data written at offset = 0x02
xrt84l38 53 rev. 1.0.1 octal t1/e1/j1 framer dma-0 w rite dma i nterface dma 0 controller interface handles data transfer between external memory and the selected transmit hdlc buffer. the dma cycle starts when the xrt84l38 asserts the req 0 output pin. the external dma controller then responds by asserting the ack0 input pin. the contents of the microprocessor interface bi-directional data bus are latched into the xrt84l38 each time the pwrl (write strobe) input pin is strobed ?low?. the xrt84l38 ends the dma cycle by negating the dma r equest input ( req 0) while wr is still active. the external dma controller acknowledges the end of dma transfer by driving the ack0 input pin ?high?. 1.5 memory and register map this section presents a complete list of the framer external memory address map and the internal memory map. in addition, the allocations of the three internal storage spaces is depicted. 1.5.1 memory mapped i/o indirect addressing the xrt84l38 employs a complete indirect addressing approach for the microprocessor interface; in order to support multiple channel implementations, maintaining rich user-controlled features, minimizing the total pin count and providing future scalability without sacrificing performance for microcontroller access. eight address bits are used with the 4 msb (most significant bits) identifying each of the eight framers channels and the 4 lsbs to address the indirect mapping registers. the xrt84l38 framer has approximately 5,800 addressable spaces internally. if each of these addresses has to be accessed directly, it would require a 13-bit address bus. in order to control total pin count as well as to provide future scalability, the xrt84l38 employs an indirect addressing scheme. using this technique, only 7 address input pins on the xrt84l38 are needed. the addressable spaces within the xrt84l38 are divided into groups of registers. each register group consists of a specific number of indirect address registers and a same number of indirect data registers with the exception of lapd buffer 0 and 1. of the 7 total address input bits, the 3 msb pins are used to identify each of eight t1/e1 framer channels. the remaining 4 lsb bits are used to address the register groups. table 8 indicates the address mapping of all the register groups within the xrt84l38. please note that the indirect address registers are with even addresses and the corresponding indirect data registers are with odd addresses with the exception of, again, the lapd buffer 0 and 1. the n corresponds to the channel number. f igure 16. dma m ode for the xrt84l38 and a m icroprocessor req[1:0] ack[1:0] wr rd pclk data[7:0] microprocessor xrt84l38
xrt84l38 54 octal t1/e1/j1 framer rev. 1.0.1 to access each individual register inside each group, a two-step access by the micro-controller to the xrt84l38 is required. in the first step, a micro-controller write access specifying the indirect address for that register within the register group should be done to the indirect address register of that group. in the second step, a micro-controller read or write should access the indirect data register of that group. for example, in order to write 0dh into the framing select register of channel 5 (address 0x50h>07h), one needs to do the following: wr 0x50 0x07 write 0x07hex into the indirect address register (0x50hex) to specify address of the framing select register within the control register group. wr 0x51 0x0d actually write value 0x0dhex into the indirect data register (0x51hex) of the control register group. the value of the indirect address register will increment after each access of the corresponding indirect data register. using the above example for illustration, after write to the indirect data register (0x51hex), the value stored inside the indirect address register (0x50hex) would become 0x08hex. this feature can greatly enhance the users' ability to access consecutive locations within a certain register group. for lapd buffer 0 and 1 with addresses 0x06hex and 0x07hex respectively, there is no indirect address register. a micro-controller write access to these data registers will access the lapd transmit buffers and a micro-controller read will access the lapd receive buffers. the very first access of the lapd buffers will always to location 0. after each access, the pointer within the lapd buffer will automatically increment by one, making further access to the next location within the buffer. user should keep track of the current location inside the buffer the read or write is associated with. t able 8: a ddress m ap a ddress c ontents n_0h channel_n - control register indirect address register n_1h channel_n - control register indirect data register n_2h channel_n - channel control indirect address register n_3h channel_n - channel control indirect data register n_4h channel_n - receive signaling array indirect address register n_5h channel_n - receive signaling array indirect data register n_6h channel_n - lapd buffer 0 indirect data register n_7h channel_n - lapd buffer 1 indirect data register n_8h channel_n - performance monitor indirect address register n_9h channel_n - performance monitor indirect data register n_ah channel_n - interrupt indirect address register n_bh channel_n - interrupt indirect data register n_ch - n_fh reserved
xrt84l38 55 rev. 1.0.1 octal t1/e1/j1 framer 1.6 description of the control registers clock select register (csr) - t1 mode(indirect address = 0xn0h, 0x00h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 bipolar violation insertion t1, e1 select 8khz synchroniza - tion enable clock loss detection enable oscclk frequency select bit 1 oscclk frequency select bit 0 transmit timing source select bit 1 transmit timing source select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 1 b it n umber b it n ame b it t ype b it d escription 7 bipolar violation insertion r/w bipolar violation insertion: this read/write bit-field permits the user to insert bipolar vio - lation to the transmit encoder. the line coding for the ds1 signal should be bipolar. this signal - ing technique consists of transmitting a binary "0" as zero volts, while a binary "1" is transmitted as either a positive or negative pulse, opposite in polarity to the previous pulse. a bipolar viola - tion occurs when the alternate polarity rule is violated. a zero-to-one transition of the bit will cause one bipolar violation to be inserted into the outgoing data stream. 6 t1/e1 select r/w t1/e1 select: this read/write bit-field permits the user to select which mode the framer will be operating. when this bit is set to one: the framer is in t1 mode. when this bit is set to zero: the framer is in e1 mode. 5 8khz synchronization enable r/w 8khz synchronization enable: this read/write bit-field permits the user to activate and de- activate the 8khz synchronization of the framer. an 8khz external reference clock can be provided to the framer. when this bit is set to one: if the transmit clock source select bits are set to two, the trans - mit clocks of all eight channels will be synchronized to the exter - nal applied 8khz reference clock and thus have the same frequency and the same phase.
xrt84l38 56 octal t1/e1/j1 framer rev. 1.0.1 4 clock loss detection enable r/w clock loss detection enable: this read/write bit-field permits the user to enable the clock loss detection logic for the framer when the recovered receive line clock is used as transmit timing source of the framer. when this bit is set to zero: the framer disables the clock loss detection logic. when this bit is set to one: the framer enables the clock loss detection logic. if the recov - ered receive line clock is used as transmit timing source of the framer, and if clock recovered from the liu is lost, the framer can detect loss of the recovered receive line clock. upon detect - ing of this occurrence, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. n ote : this bit-field is ignored if the txserclk or the oscclk driven divided clock is chosen to be the timing source of transmit section of the framer. 3-2 oscclk frequency select r/w oscclk frequency select: these two read/write bit-fields permit the user to select inter - nal clock dividing logic of the framer depending on the frequency of incoming oscillator clock (oscclk). the frequency of internal clock used by the framer should be 12.352mhz. when these bits are set to 00: the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 12.352mhz. when these bits are set to 01: the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 24.704mhz. when these bits are set to 10: the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 49.408mhz. b it n umber b it n ame b it t ype b it d escription
xrt84l38 57 rev. 1.0.1 octal t1/e1/j1 framer 1-0 transmit timing source select r/w transmit timing source select: these two read/write bit-fields permit the user to select the timing source of transmit section of the framer. when the framer is operating at non-multiplexed mode, that is, the transmit back-plane interface is operating at a clock rate of 1.544mhz for t1, these two read/write bit-fields also deter - mine the direction of single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk). when the framer is oper - ating at other back-plane mode, the single frame synchroniza - tion pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. when these bits are set to 00: the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multi - plexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. when these bits are set to 01: the transmit serial clock is the timing source of transmit sec - tion of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame syn - chronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. when these bits are set to 10: the oscclk driven divided clock is the timing source of trans - mit section of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame syn - chronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. when these bits are set to 11: the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multi - plexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. b it n umber b it n ame b it t ype b it d escription
xrt84l38 58 octal t1/e1/j1 framer rev. 1.0.1 clock select register (csr) - e1 mode (indirect address = 0xn0h, 0x00h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 bipolar violation insertion t1, e1 select 8khz synchroniza - tion enable clock loss detection enable oscclk frequency select bit 1 oscclk frequency select bit 0 transmit timing source select bit1 transmit timing source select bit0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 1 b it n umber b it n ame b it t ype b it d escription 7 bipolar violation insertion r/w bipolar violation insertion: this read/write bit-field permits the user to insert bipolar vio - lation to the transmit encoder. the line coding for the ds1 signal should be bipolar. this signal - ing technique consists of transmitting a binary "0" as zero volts, while a binary "1" is transmitted as either a positive or negative pulse, opposite in polarity to the previous pulse. a bipolar viola - tion occurs when the alternate polarity rule is violated. a zero-to-one transition of the bit will cause one bipolar violation to be inserted into the outgoing data stream. 6 t1/e1 select r/w t1/e1 select: this read/write bit-field permits the user to select which mode the framer will be operating. when this bit is set to one: the framer is in t1 mode. when this bit is set to zero: the framer is in e1 mode. 5 8khz synchronization enable r/w 8khz synchronization enable: this read/write bit-field permits the user to activate and de- activate the 8khz synchronization of the framer. an 8khz external reference clock can be provided to the framer. when this bit is set to one: if the transmit clock source select bits are set to two, the trans - mit clocks of all eight channels will be synchronized to the exter - nal applied 8khz reference clock and thus have the same frequency and the same phase.
xrt84l38 59 rev. 1.0.1 octal t1/e1/j1 framer 4 clock loss detection enable r/w clock loss detection enable: this read/write bit-field permits the user to enable the clock loss detection logic for the framer when the recovered receive line clock is used as transmit timing source of the framer. when this bit is set to zero: the framer disables the clock loss detection logic. when this bit is set to one: the framer enables the clock loss detection logic. if the recov - ered receive line clock is used as transmit timing source of the framer, and if clock recovered from the liu is lost, the framer can detect loss of the recovered receive line clock. upon detect - ing of this occurrence, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. n ote : this bit-field is ignored if the txserclk or the oscclk driven divided clock is chosen to be the timing source of transmit section of the framer. 3-2 oscclk frequency select r/w oscclk frequency select: these two read/write bit-fields permit the user to select inter - nal clock dividing logic of the framer depending on the frequency of incoming oscillator clock (oscclk). the frequency of internal clock used by the framer should be 16.384mhz. when these bits are set to 00: the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 16.384mhz. when these bits are set to 01: the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 32.768mhz. when these bits are set to 10: the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 65.536mhz. b it n umber b it n ame b it t ype b it d escription
xrt84l38 60 octal t1/e1/j1 framer rev. 1.0.1 1-0 transmit timing source select r/w transmit timing source select: these two read/write bit-fields permit the user to select the timing source of transmit section of the framer. when the framer is operating at non-multiplexed mode, that is, the transmit back-plane interface is operating at a clock rate of 2.048mhz for t1, these two read/write bit-fields also deter - mine the direction of single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk). when the framer is oper - ating at other back-plane mode, the single frame synchroniza - tion pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. when these bits are set to 00: the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multi - plexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. when these bits are set to 01: the transmit serial clock is the timing source of transmit sec - tion of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame syn - chronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. when these bits are set to 10: the oscclk driven divided clock is the timing source of trans - mit section of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame syn - chronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. when these bits are set to 11: the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multi - plexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. b it n umber b it n ame b it t ype b it d escription
xrt84l38 61 rev. 1.0.1 octal t1/e1/j1 framer line interface control register (licr) - t1 mode (indirect address = 0xn0h, 0x01h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 force transmit los nrz rail select loop-back select bit 1 loop-back select bit 0 transmit line clock inversion receive line clock inversion transmit b8zs enable receive b8zs enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 force transmit los r/w force transmit los: this read/write bit-field forces the framer to transmit loss of signal (los) onto the liu interface. when this bit is set to one: the framer is forced to transmit an los signal onto the liu inter - face outputs. 6 nrz rail select r/w nrz rail select: this read/write bit-field permits the user to select how data are transmitted to and received from the liu. when this bit is set to zero: the framer is operating in dual-rail mode. the txpos pin is car - rying the positive data and the txneg pin is carrying the nega - tive data. the positive and the negative data combined represent the entire data stream going to the liu. the received data from the liu will also be bipolar, that is, the positive data received from rxpos and the negative data received from rxneg combined represent the entire data stream. when this bit is set to one: the framer is operating in single-rail mode. the txpos pin is carrying the entire data stream. the txneg pin is carrying the multi-frame synchronization pulse. the received data from the liu will also be single-railed. the rxpos pin is carrying the entire data stream going into the framer from liu.
xrt84l38 62 octal t1/e1/j1 framer rev. 1.0.1 5-4 loop-back select r/w loop-back select: these read/write bit-fields permit the user to configure any channel of the framer to operate in different loop-back modes. each channel of the framer can operate in three loop-back modes: local loop-back (ll), far-end line loop-back (fell) and pay - load loop-back (pl).local loop-back connects the transmitter output of the framer back to the receiver input. all payload data as well as data link bits and frame alignment bits are directed back into the framer. the local-loop-back allows the perfor - mance of diagnostic tests on the transmitter and receiver to ver - ify operation of the framer and equipment-side circuitry. payload loop-back also connects the transmitter output of the framer back to the receiver input. however, only payload data and frame alignment bits are directed back into the framer. the framer can still transmit data link information to the remote termi - nal. the payload loop-back allows the performance of diagnos - tic tests on the transmitter and receiver to verify operation of the framer and equipment-side circuitry. at the same time, the pay - load loop-back allows performance report and test signal identi - fication message to be sent to remote side. far-end line loop-back connects the receiver input to the trans - mit output. only the liu interface logic inside the framer can be examined using this loop-back mode. during the far-end line loop-back, the recovered receive line clock will automatically be the source of the transmit line clock. when these bits are set to 00: the framer is operating in normal mode; no loop-back mode is selected. when these bits are set to 01: the framer is operating in local loop-back mode. when these bits are set to 10: the framer is operating in far-end line loop-back mode. when these bits are set to 11: the framer is operating in payload loop-back mode. 3 transmit line clock inversion r/w transmit line clock inversion: this read/write bit-field permits the user to select which edge of the transmit line clock will data transition occur. when this bit is set to zero: the transmit data transition occurs at rising edge of the transmit line clock. the user should program the liu device to sample data at falling edge of the transmit line clock. when this bit is set to one: the transmit data transition occurs at falling edge of the transmit line clock. the user should program the liu device to sample data at rising edge of the transmit line clock. b it n umber b it n ame b it t ype b it d escription
xrt84l38 63 rev. 1.0.1 octal t1/e1/j1 framer 2 receive line clock inver - sion r/w receive line clock inversion: this read/write bit-field permits the user to select which edge of the receive line clock will be used by the framer to sample incoming data from liu. when this bit is set to zero: the receive data transition occurs at rising edge of the receive line clock. the framer will sample data at falling edge of the receive line clock. when this bit is set to one: the receive data transition occurs at falling edge of the receive line clock. the frame will sample data at rising edge of the receive line clock. 1 transmit b8zs enable r/w transmit b8zs enable: this read/write bit-field permits the user to enable transmit b8zs encoding. when this bit is set to zero: the framer will send out transmit data encoded by b8zs. the user should turn off the b8zs encoding of the liu device. when this bit is set to one: the framer will send out transmit data in ami line code without b8zs encoding. the user should turn on or off b8zs encoding of the liu device depending on system requirement. 0 receive b8zs enable r/w receive b8zs enable: this read/write bit-field permits the user to enable receive b8zs decoding. when this bit is set to zero:the framer will decode the incoming data assuming that they are b8zs encoded.when this bit is set to one:the framer disables b8zs decoding of the incoming data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 64 octal t1/e1/j1 framer rev. 1.0.1 line control register (lcr) (indirect address = 0xn0h, 0x02h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 gpio direction control bit 3 gpio direction control bit 2 gpio direction control bit 1 gpio direction control bit 0 gpio bit 3 gpio bit 2 gpio bit 1 gpio bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-4 gpio direction control r/w gpio direction control: these read/write bit-fields control directions of the four on- chip general purpose input/output pins. when these bits are set to zero: the corresponding gpio pins are configured as inputs. the user can now apply signals to the gpio pins by writing to the corre - sponding gpio bit-fields. when these bits are set to one: the corresponding gpio pins are configured as outputs. the user can read the output values by reading the corresponding gpio bit-fields. 3-0 gpio r/w gpio: these read/write bit-fields contain values of the four on-chip general purpose input/output pins. when the corresponding gpio direction control bit-fields are set to zero, the gpio pins are configured as inputs. the gpio bit-fields contain values to be present on the gpio pins. for example, if the user wants to pull the pin gpio_0 high, he/she can write zero into the gpio direction control bit 0; then write one into the gpio bit 0. when the corresponding gpio direction control bit-fields are set to one, the gpio pins are configured as outputs. the gpio bit-fields contain values currently present on the gpio pins. liu access register 1 (lar1) (indirect address = 0xn0h, 0x03h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lar1 bit 7 lar1 bit 6 lar1 bit 5 lar1 bit 4 lar1 bit 3 lar1 bit 2 lar1 bit 1 lar1 bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 lar1 r/w
xrt84l38 65 rev. 1.0.1 octal t1/e1/j1 framer liu access register 2 (lar2) (indirect address = 0xn0h, 0x04h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lar2 bit 7 lar2 bit 6 lar2 bit 5 lar2 bit 4 lar2 bit 3 lar2 bit 2 lar2 bit 1 lar2 bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 lar2 r/w liu poll register 1 (lpr1) (indirect address = 0xn0h, 0x05h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lpr1 bit 7 lpr1 bit 6 lpr1 bit 5 lpr1 bit 4 lpr1 bit 3 lpr1 bit 2 lpr1 bit 1 lpr1 bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 lpr1 r/w liu poll register 2 (lpr2) (indirect address = 0xn0h, 0x06h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lpr2 bit 7 lpr2 bit 6 lpr2 bit 5 lpr2 bit 4 lpr2 bit 3 lpr2 bit 2 lpr2 bit 1 lpr2 bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 lpr2 r/w
xrt84l38 66 octal t1/e1/j1 framer rev. 1.0.1 framing select register (fsr) - t1 mode (indirect address = 0xn0h, 0x07h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling update on super-frame boundary crc diagnostics select j1 crc calculation one synchroniza - ti on candidate only fast synchroniza - tion t1 framing select bit 2 t1 framing select bit 1 t1 framing select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 signaling update on super-frame boundary r/w signaling update on super-frame boundary: this read/write bit-field controls the framer to update signal - ing data only on super-frame boundaries. the user can insert signaling data to the framer through the txsig_n input pins or by writing into the transmit signaling con - trol registers (tscr). when this bit is set to zero: the framer will update signaling data once it is received. that is, any value presents on the txsig_n pins or any value pro - grammed to the tscr will be inserted into the outgoing data stream right away. also, any changes on the txsig_n pins or the tscr will be instantaneously reflected on the outgoing data stream. when this bit is set to one: the framer will only update signaling data on super-frame boundaries. any changes on the txsig_n pins or the tscr will be ignored until the next super-frame boundary is reached. 6 crc diagnostics select r/w crc diagnostics select: this read/write bit-field allows the user to insert crc errors into outgoing data stream. a transition from zero to one of this bit will prompt the framer to invert the value of one crc bit. when this bit is set to zero: the framer will operate normally and there is no insertion of erro - neous crc bit. when this bit is set to one: one crc error will be inserted into the outgoing data stream when this bit is transitioned from zero to one. n ote : to send another crc error, the framer has to reset this bit to zero and set it to one again.
xrt84l38 67 rev. 1.0.1 octal t1/e1/j1 framer 5 j1 crc calculation r/w j1 crc calculation: this read/write bit-field forces the framer to calculate crc-6 bits in j1 format.in j1 format, crc-6 calculation is done based on the actual values of all payload bits as well as the framing bits. in ds1 format, crc-6 calculation is done based on the pay - load bits only while assuming all the framing bits are one. when this bit is set to zero: the framer will perform crc-6 calculation in ds1 format. when this bit is set to one: the framer will perform crc-6 calculation in j1 format. this fea - ture permits the driver to comply with j1 standard. 4 one synchronization candidate only r/w one synchronization candidate only: this read/write bit-field forces the framing search engine of the framer to declare synchronization while there is one and only one candidate left. 3 fast synchronization r/w fast synchronization: this read/write bit-field permits the framing search engine of the framer to declare synchronization earlier. 2-0 t1 framing select r/w t1 framing select: these read/write bit-fields allow the user to select one of the five t1 framing formats supported by the framer. these framing formats include esf, slc ? 96, sf, n and t1dm mode. n ote : changing of framing format will automatically force the framer to resync. b it n umber b it n ame b it t ype b it d escription esf slc?96 sf n framing format t1dm bit 2 bit 1 bit 0 0 1 1 1 1 x 0 0 1 1 x 0 1 0 1
xrt84l38 68 octal t1/e1/j1 framer rev. 1.0.1 framing select register (fsr) - e1 mode (indirect address = 0xn0h, 0x07h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 annex b enable crc diagnostics select cas selection bit 1 cas selection bit 0 crc-4 selection bit 1 crc-4 selection bit 0 fas alignment frame check sequence enable fas selection bit r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 annex b enable r/w signaling update on super-frame boundary: this read/write bit-field controls the framer to be compliant with itu-t recommendation g.706 annex b for crc-to-non- crc internetworking detection. when this bit is set to zero: the framer will operate in normal condition. that is, itu-t g.706 annex b is disabled. when this bit is set to one: the framer will enable support of itu-t g.706 annex b. 6 crc diagnostics select r/w crc diagnostics select: this read/write bit-field allows the user to insert crc errors into outgoing data stream. a transition from zero to one of this bit will prompt the framer to invert the value of one crc bit. when this bit is set to zero: the framer will operate normally and there is no insertion of erro - neous crc bit. when this bit is set to one: one crc error will be inserted into the outgoing data stream when this bit is transitioned from zero to one.note:to send another crc error, the framer has to reset this bit to zero and set it to one again.
xrt84l38 69 rev. 1.0.1 octal t1/e1/j1 framer 5-4 cas selection bit r/w cas selection: these read/write bit fields allow the user to enable searching of cas multi-frame alignment and determine which algorithm of the two are used for locking the cas multi-frame alignment pattern. when these bits are set to 00: searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. when these bits are set to 01: searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchro - nization using algorithm 1. when these bits are set to 10: searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchro - nization using algorithm 2 (g.732). when these bits are set to 11: searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. b it n umber b it n ame b it t ype b it d escription
xrt84l38 70 octal t1/e1/j1 framer rev. 1.0.1 3-2 crc-4 selection bit r/w crc-4 selection: these read/write bit fields allow the user to enable searching of crc-4 multi-frame alignment and determine what criteria are used for locking the crc-4 multi-frame alignment pattern. when these bit s are set to 00: searching of crc-4 multi-frame alignment is disabled. the xrt84l38 framer will not search for crc-4 multi-frame align - ment and thus will not declare crc-4 multi-frame synchroniza - tion. no receive crc-4 multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. when these bit s are set to 01: searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame syn - chronization if: at least one valid crc-4 multi-frame alignment signal is observed within 8 ms. when these bit s are set to 10: searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame syn - chronization if: at least two valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 mult i-frame alignment signals is multiple of 2 ms. when these bit s are set to 11: searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame syn - chronization if: at least three valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 mult i-frame alignment signals is multiple of 2 ms. 1 fas alignment frame check sequence enable r/w fas alignment frame check sequence enable: this read/write bit-field enables frame check sequence in fas alignment process. the frame check sequence consists of verifying correct frame alignment for an additional two frames. when this bit is set to 0: the frame check sequence is disabled in fas alignment pro - cess. when this bit is set to 1: the frame check sequence is enabled in fas alignment pro - cess. b it n umber b it n ame b it t ype b it d escription
xrt84l38 71 rev. 1.0.1 octal t1/e1/j1 framer 0 fas selection bit r/w fas selection: this read/write bit field allows the user to determine which algo - rithm is used for searching fas frame alignment pattern. when an fas alignment pattern is found and locked, the xrt84l38 will generate receive synchronization (rxsync_n) pulse. when this bit is set to 0: algorithm 1 is selected for searching fas frame alignment pat - tern. when this bit is set to 1: algorithm 2 is selected for searching fas frame alignment pat - tern. alarm generation register (agr) - t1 mode (indirect address = 0xn0h, 0x08h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved loss of frame dec - laration enable yellow alarm generation select bit 1 ye ll ow a la rm generation select bit 0 alarm indication signal generation select bit 1 alarm indication signal generation select bit 0 alarm indication signal detection select bit 1 alarm indication signal detection select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 reserved x 6 loss of frame declaration enable r/w loss of frame declaration enable: this read/write bit-field permits the framer to declare red alarm in case of loss of frame alignment (lof). when receiver module of the framer detects loss of frame alignment in the incoming data stream, it will generate a red alarm. the framer will also generate an rxlofs interrupt to notify the microprocessor that an lof condition is occurred. a yellow alarm is then returned to the remote transmitter to report that the local receiver detects lof. when this bit is set to zero: red alarm declaration is disabled. when this bit is set to one: red alarm declaration is enabled. b it n umber b it n ame b it t ype b it d escription
xrt84l38 72 octal t1/e1/j1 framer rev. 1.0.1 5-4 yellow alarm generation select r/w yellow alarm generation select: these read/write bit-fields activate and de-activate transmis - sion of yellow alarm by the framer. in various framing formats, the pattern and duration of yellow alarm various. the following text describes how the framer transmits yellow alarm by setting these bit-fields to different values. sf mode: when these bits are set to 00: transmission of yellow alarm is disabled. when these bits are set to 01: the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero. when these bits are set to 10: the framer transmits yellow alarm by sending the super-frame alignment bit (fs) of frame 12 as one. when these bits are set to 11: the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero.n mode: when these bits are set to 00: transmission of yellow alarm is disabled. when these bits are set to 01, 10 or 11: the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero. esf mode: when the framer is in esf mode, it transmits yellow alarm pat - tern of eight ones followed by eight zeros (1111_1111_0000_0000) through the 4kbit/s data link bits. when the yellow alarm generation select bits are set to 00: transmission of yellow alarm is disabled. when these bits are set to 01: the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. b it n umber b it n ame b it t ype b it d escription
xrt84l38 73 rev. 1.0.1 octal t1/e1/j1 framer when these bits are set to 10: bit 1 of the yellow alarm generation select forms a pulse that controls the duration of yellow alarm transmission. the alarm continues until bit 1 goes low. when these bits are set to 11: the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. t1dm mode: when these bits are set to 00: transmission of yellow alarm is disabled. when these bits are set to 01, 10 or 11: the framer transmits yellow alarm by setting the yellow alarm bit (y-bit) to zero. 3-2 alarm indication signal generation select r/w alarm indication signal generation select: these read/write bit-fields activate and de-activate transmis - sion of alarm indication signal (ais). there are two types of alarm indication signals - framed and unframed. a unframed ais signal is all-ones including all the framing bits. a framed ais signal is all-ones except the framing bits. when these bits are set to 00: the framer will disable ais alarm generation. when these bits are set to 01: the framer will transmit unframed ais alarm. when these bits are set to 10: the framer will disable ais alarm generation. when these bits are set to 11: the framer will transmit framed ais alarm. 1-0 alarm indication signal detection select r/w alarm indication signal detection select: these read/write bit-fields activate and de-activate alarm indication signal detection of the framer. when these bits are set to 00: the framer disables detection of ais alarm. when these bits are set to 01: the framer enables detection of unframed ais alarm. when these bits are set to 10: the framer disables detection of ais alarm. when these bits are set to 11: the framer enables detection of framed ais alarm. b it n umber b it n ame b it t ype b it d escription
xrt84l38 74 octal t1/e1/j1 framer rev. 1.0.1 alarm generation register (agr) - e1 mode (indirect address = 0xn0h, 0x08h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 auxp enable loss of frame dec - laration enable yellow alarm generation select bit 1 ye ll ow a la rm generation select bit 0 alarm indication signal generation select bit 1 alar m indication signal generation select bit 0 alarm indication signal detection select bit 1 alarm indication signal detection select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 auxp enable r/w auxp enable: auxp is an unframed 1010 pattern. when this bit is set to zero: auxp generation is disabled. when this bit is set to one: auxp generation is enabled. 6 loss of frame declaration enable r/w loss of frame declaration enable: this read/write bit-field permits the framer to declare red alarm in case of loss of frame alignment (lof). when receiver module of the framer detects loss of frame alignment in the incoming data stream, it will generate a red alarm. the framer will also generate an rxlofs interrupt to notify the microprocessor that an lof condition is occurred. a yellow alarm is then returned to the remote transmitter to report that the local receiver detects lof. when this bit is set to zero: red alarm declaration is disabled. when this bit is set to one: red alarm declaration is enabled.
xrt84l38 75 rev. 1.0.1 octal t1/e1/j1 framer 5-4 yellow alarm generation select r/w yellow alarm generation select: these read/write bit-fields allows the user to choose how the xrt84l38 would generate yellow alarm and cas multi-frame yellow alarm. when these bits are set to 00: transmission of yellow alarm and cas multi-frame yellow alarm is disabled. when these bits are set to 01: the yellow alarm bit is transmitted by echoing the received fas alignment pattern. if the correct fas alignment is received, the yellow alarm bit is set to zero. if the fas alignment pattern is missing or corrupted, the yellow alarm bit is set to one. the cas multi-frame yellow alarm bit is transmitted by echoing the received cas multi-frame alignment pattern (the four zeros pattern). if the correct cas multi-frame alignment is received, the cas multi-frame yellow alarm bit is set to zero. if the cas multi-frame alignment pattern is missing or corrupted, the cas multi-frame yellow alarm bit is set to one. when these bits are set to 10: the yellow alarm and cas multi-frame yellow alarms are trans - mitted as zero. when these bits are set to 11: the yellow alarm and cas multi-frame yellow alarms are trans - mitted as one. 3-2 alarm indication signal generation select r/w alarm indication signal generation select: these read/write bit-fields activate and de-activate transmis - sion of alarm indication signal (ais). there are two types of alarm indication signals - framed and unframed. a unframed ais signal is all-ones including all the framing bits. a framed ais signal is all-ones except the framing bits. when these bits are set to 00: the framer will disable ais alarm generation. when these bits are set to 01: the framer will transmit unframed ais alarm. when these bits are set to 10: the framer will generate ais16. only time slot 16 is carrying the all ones pattern. the other time slots still carry framing and pcm data. when these bits are set to 11: the framer will transmit framed ais alarm. b it n umber b it n ame b it t ype b it d escription
xrt84l38 76 octal t1/e1/j1 framer rev. 1.0.1 1-0 alarm indication signal detection select r/w alarm indication signal detection select: these read/write bit-fields activate and de-activate alarm indication signal detection of the framer. when these bits are set to 00: the framer disables detection of ais alarm. when these bits are set to 01: the framer enables detection of unframed ais alarm. when these bits are set to 10: the framer enables detection of ais16 alarm. when these bits are set to 11: the framer enables detection of framed ais alarm. synchronization mux register (smr) - t1 mode (indirect address = 0xn0h, 0x09h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved transmit multi-frame alignment transmit super-frame synchroniza - tion synchroniza - tion signal direction reserved reserved crc-6 source framing bit source r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 reserved r/w 6 transmit multi-frame alignment r/w transmit multi-frame alignment: this read/write bit-field forces the framer to align the trans - mit multi-frame boundary with the back-plane multi-frame syn - chronization pulse. when this bit is set to zero: the transmit multi-frame boundary is not aligned with the back- plane multi-frame synchronization pulse. when this bit is set to one: the transmit multi-frame boundary is forced to align with the back-plane multi-frame synchronization pulse. b it n umber b it n ame b it t ype b it d escription
xrt84l38 77 rev. 1.0.1 octal t1/e1/j1 framer 5 transmit super-frame synchronization r/w transmit super-frame synchronization: this read/write bit-field determines the transmit synchroniza - tion input signal (txsync) being either the frame synchroniza - tion signal or the multi-frame synchronization signal. when this bit is set to zero: the transmit synchronization input signal (txsync) is the frame synchronization signal that indicates the frame boundary. in 1.544mbit/s basic mode, the transmit multi-frame synchroniza - tion input signal (txmsync) indicates the multi-frame boundary. in other back-plane modes, the txmsync input is an input trans - mit clock. when this bit is set to one: the transmit synchronization input signal (txsync) is the trans - mit multi-frame synchronization signal indicating the multi-frame boundary. 4 synchronization signal direction r/w synchronization signal direction: this read/write bit-field determines the direction of transmit synchronization signal (txsync_n) and the transmit multi-frame synchronization signal (txmsync_n). in h.100 interface mode, this read/write bit-field determines the location of the trans - mit synchronization pulse. when this bit is set to zero: the transmit synchronization signal is input if the transmit line clock source select bits of clock select register (csr) equal to one. if the transmit line clock source select bits of clock select register (csr) is not equal to one, the transmit synchro - nization signal is output. in h.100 interface mode, the transmit synchronization pulse occurs at the last and the first clock cycles of each frame. when this bit is set to one: the transmit synchronization signal is output if the transmit line clock source select bits of clock select register (csr) equal to one. if the transmit line clock source select bits of clock select register (csr) is not equal to one, the transmit synchro - nization signal is input. in h.100 interface mode, the transmit synchronization pulse occurs at the first two clock cycles of each frame. 3-2 reserved r/w 1 crc-6 source r/w crc-6 source: this read/write bit-field permits the user to determine where the crc-6 bits should be inserted. when this bit is zero: the crc-6 bits are gener ated and inserted by the framer inter - nally. when this bit is one: if the framer is operating in no rmal 1.544mbit/s mode, the crc-6 bits are passed through from the transmit serial data input (txser_n). b it n umber b it n ame b it t ype b it d escription
xrt84l38 78 octal t1/e1/j1 framer rev. 1.0.1 0 framing bit source r/w framing bit source: this read/write bit-field permits the user to determine where the framing alignment bits should be inserted. when this bit is zero: the framing alignment bits are generated and inserted by the framer internally. when this bit is one: if the framer is operating in normal 1.544mbit/s mode, the fram - ing alignment bits are passed through from the transmit serial data input (txser_n). synchronization mux register (smr) - e1 mode (indirect address = 0xn0h, 0x09h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 e bit source select bit 1 e bit source select bit 0 reserved synchroniza - tion signal direction transmit data link source select bit 1 transmit data link source select bit 0 crc-4 source framing bit source r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-6 e bit source select r/w e source select: these read/write bit-fields permits the user to determine where the e bits should be inserted and what the e bits should be. when these bits are 00: the e bits are generated and inserted by the framer internally. when these bits are 01: the e bits are forced to be "0" and are inserted by the framer internally. when these bits are 10:the e bits are forced to be "1" and are inserted by the framer internally. when these bits are 11: source of the e bits is hdlc controller of the framer. the e bits are used to carry data link messages. 5 reserved b it n umber b it n ame b it t ype b it d escription
xrt84l38 79 rev. 1.0.1 octal t1/e1/j1 framer 4 synchronization signal direction r/w synchronization signal direction: this read/write bit-field determines the direction of transmit synchronization signal (txsync_n) and the transmit multi-frame synchronization signal (txmsync_n). in h.100 interface mode, this read/write bit-field determines the location of the trans - mit synchronization pulse. when this bit is set to zero: the transmit synchronization signal is input if the transmit line clock source select bits of clock select register (csr) equal to one. that is, if the transmit serial input clock (txserclk_n) is configured as the source of the transmit line clock. if the transmit line clock source select bits of clock select register (csr) is not equal to one, the transmit synchronization signal is output. in h.100 interface mode, the transmit synchronization pulse occurs at the last and the first clock cycles of each frame. when this bit is set to one: the transmit synchronization signal is output if the transmit line clock source select bits of clock select register (csr) equal to one. that is, if the transmit serial input clock (txserclk_n) is configured as the source of the transmit line clock. if the transmit line clock source select bits of clock select register (csr) is not equal to one, the transmit synchronization signal is input. in h.100 interface mode, the transmit synchronization pulse occurs at the first two clock cycles of each frame. 3-2 transmit data link source select [1:0] r/w transmit data link source select [1:0]: these read/write bit-fields permits the user to determine where the data link bits should be inserted from. when these bits are set to 00: the data link bits are inserted into the framer through the trans - mit serial data input interface via the txser_n pins. when these bits are set to 01: the data link bits are inserted into the framer through the trans - mit hdlc controller. when these bits are set to 10: the data link bits are inserted into the framer through the trans - mit overhead input interface via the txoh_n pins. when these bits are set to 11: the data link bits are inserted into the framer through the trans - mit serial data input interface via the txser_n pins. b it n umber b it n ame b it t ype b it d escription
xrt84l38 80 octal t1/e1/j1 framer rev. 1.0.1 1 crc-4 source select r/w crc-4 source select: this read/write bit-field permits the user to determine where the crc-4 bits should be inserted. when this bit is set to 0: the crc-4 bits are gener ated and inserted by the framer inter - nally. when this bit is set to 1: if the framer is operating in no rmal 2.048mbit/s mode, the crc-4 bits are generated by external equipment and passed through from the transmit serial data input interface block via the txser_n pin. 0 framing bit source r/w framing bit source: this read/write bit-field permits the user to determine where the framing alignment bits should be inserted. when this bit is set to 0: the framing alignment bits are generated and inserted by the framer internally. when this bit is set to 1: if the framer is operating in normal 2.048mbit/s mode, the fram - ing alignment bits are passed through from the transmit serial data input interface block via the txser_n pin. transmit signaling and data link select register (tsdlsr)- t1 mode (indirect address = 0xn0h, 0x0ah) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved reserved transmit d a t a l i n k bandwidth select bit 1 transmit d a t a l i n k bandwidth select bit 0 d/e timeslot source select bit 1 d/e timeslot source select bit 0 data link source select bit 1 data link source select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-6 reserved r/w b it n umber b it n ame b it t ype b it d escription
xrt84l38 81 rev. 1.0.1 octal t1/e1/j1 framer 5-4 transmit data link band - width select r/w transmit data link bandwidth select: these read/write bit-fields determined the bandwidth of facility data link channel of the framer when operating in esf mode. when these bits are set to 00: the facility data link is a 4khz channel. all available fdl bits (first bit of every other frame) are used as data link bits. when these bits are set to 01: the facility data link is a 2khz channel. only the odd fdl bits (first bit of frame 1, 5, 9?) are used as data link bits. when these bits are set to 10: the facility data link is a 2khz channel. only the even fdl bits (first bit of frame 3, 7, 11?) are used as data link bits. 3-2 d/e timeslot source select r/w d/e timeslot source select: these read/write bit-fields permit the user to select data source of d or e channel (d/e timeslot) for the isdn primary rate interface, if lapdsel[1:0] bits in tccr is 10. n ote : the lapd select (lapdsel) bits of the transmit channel control register (tccr) determine which one of the three lapd channel are used for d/e timeslot. if lapdsel[1:0] = 10, the d/e timeslot source select bits will determine the data source for d/e time slot. the isdn primary rate interface (isdn i.431) can carry b chan - nel, d channel, e channel and h channel. b channel has a bit rate of 64kbit/s and is equivalent to a ds0 channel in t1 used for payload transmission. d channel has a bit rate of 64kbit/s and is used primarily for signaling transmission. e channel has a bit rate of 64kbit/s and is used for signaling for circuit switching. it is used only with multiple-access configuration. h channel has bit rates of 384kbit/s, 1536kbit/s for t1 primary rate, and 1920kbit/s for e1 primary rate. the signaling information presented on d or e channels are pro - vided by several sources. the user can provide the signaling information through the transmit serial data via the txser_n pins. the user can also supply the signaling data by writing to the lapd controller using microprocessor access. finally, the user can provide the data through fraction t1 input via the txfrt1_n pins. when these bits are set to 00: the d or e channel data are inserted from the transmit serial data input. when these bits are set to 01: the d or e channel data are inserted from the lapd controllers. the user can read or write to the lapd controller using micro - processor access. when these bits are set to 10: the d or e channel data are inserted from the transmit serial data input. when these bits are set to 11: the d or e channel data are inserted from the fractional t1 input. b it n umber b it n ame b it t ype b it d escription
xrt84l38 82 octal t1/e1/j1 framer rev. 1.0.1 1-0 data link source select r/w data link source select: these read/write bit-fields permit the user to select data source of the facility data link bits. the user can insert facility data link bits into the framer through the lapd controller or slca96 buffer. both lapd controller and slca96 buffer can be programmed through microprocessor access. the user can also insert facility data link bits through transmit serial data directly via txser_n pins. overhead inter - face of the framer can also be used to input facility data link bits. finally, the user can force these data link bits to one. when these bits are set to 00: the facility data link bits are inserted into the framer through either the lapd controller or the slca96 buffer. when these bits are set to 01: the facility data link bits are inserted into the framer through the transmit serial data input. when these bits are set to 10: the facility data link bits are inserted into the framer through the overhead interface via the txoh_n pins. when these bits are set to 11: the facility data link bits are forced to one by the framer. transmit signaling and data link select register (tsdlsr)- e1 mode (indirect address = 0xn0h, 0x0ah) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa8 data link select transmit sa7 data link select transmit sa6 data link select transmit sa5 data link select transmit sa4 data link select data link source select bit 2 data link source select bit 1 data link source select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 transmit sa8 data link select r/w transmit sa8 data link select: when this bit is set to 0: source of the sa8 nation bit is not from the data link interface. when this bit is set to 1: source the sa8 national bit from the data link interface. 6 transmit sa7 data link select r/w transmit sa7 data link select: when this bit is set to 0: source of the sa7 nation bit is not from the data link interface. when this bit is set to 1: source the sa7 national bit from the data link interface. b it n umber b it n ame b it t ype b it d escription
xrt84l38 83 rev. 1.0.1 octal t1/e1/j1 framer 5 transmit sa6 data link select r/w transmit sa6 data link select: when this bit is set to 0: source of the sa6 nation bit is not from the data link interface. when this bit is set to 1: source the sa6 national bit from the data link interface. 4 transmit sa5 data link select r/w transmit sa5 data link select: when this bit is set to 0: source of the sa5 nation bit is not from the data link interface. when this bit is set to 1: source the sa5 national bit from the data link interface. 3 transmit sa4 data link select r/w transmit sa4 data link select: when this bit is set to 0: source of the sa4 nation bit is not from the data link interface. when this bit is set to 1: source the sa4 national bit from the data link interface. 2-0 transmit signaling and data link select r/w transmit signaling and data link select: these read/write bit-fields permit the user to select data source of the d or e channels, the national bits and the time slot 16 octets. national bits when these bits are set to 000: the data link interface is source of the sa4 through sa8 nation bits, if the corresponding transmit sa data link select bit(s) (bit 3 to bit 7 of the transmit signaling and data link select regis - ter) are set to 1. when these bits are set to 001: the data link interface is source of the sa4 through sa8 nation bits, if the corresponding transmit sa data link select bit(s) (bit 3 to bit 7 of the transmit signaling and data link select regis - ter) are set to 1. when these bits are set to 010: the sa4 through sa8 nation bits are forced to 1. when these bits are set to 011: the sa4 through sa8 nation bits are forced to 1. when these bits are set to 100: the data link interface is source of the sa4 through sa8 nation bits, if the corresponding transmit sa data link select bit(s) (bit 3 to bit 7 of the transmit signaling and data link select regis - ter) are set to 1. when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved. b it n umber b it n ame b it t ype b it d escription
xrt84l38 84 octal t1/e1/j1 framer rev. 1.0.1 timeslot 16 octet when these bits are set to 000: timeslot 16 octet is taken directly from the transmit signaling control register (tscr). when these bits are set to 001: timeslot 16 octet is taken directly from the transmit overhead input interface through the txoh_n pin or per-channel signaling registers determined by transmit signaling source bit of the transmit signaling control register (tscr)of timeslot 16. when these bits are set to 010: timeslot 16 octet is taken directly from the transmit signaling input interface through the txsig_n pin. when these bits are set to 011: timeslot 16 octet is taken directly from the transmit overhead input interface through the txoh_n pin or per-channel signaling registers determined by transmit signaling source bit of the transmit signaling control register (tscr) of timeslot 16. when these bits are set to 100: timeslot 16 octet is taken directly from the transmit signaling control register (tscr). when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved. d/e time slot when these bits are set to 000: d or e time slot data are taken through the transmit fractional data input interface (txfrtd_n pin). when these bits are set to 001: d or e time slot data are taken through the transmit fractional data input interface (txfrtd_n pin). when these bits are set to 010: d or e time slot data are taken through the transmit fractional data input interface (txfrtd_n pin). when these bits are set to 011: d or e time slot data are taken through the transmit fractional data input interface (txfrtd_n pin). when these bits are set to 100: d or e time slot data are taken through the transmit serial sig - naling input interface (txsig_n pin). when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved. the following table summaries sources of national bits, timeslot 16 octet and d or e time slots.t b it n umber b it n ame b it t ype b it d escription
xrt84l38 85 rev. 1.0.1 octal t1/e1/j1 framer framing control register (fcr) - t1 mode (indirect address = 0xn0h, 0x0bh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 force re-synchro - nization synchroniza - tion with crc verifi - cation framing error toler - ance bit 2 framing error toler - ance bit 1 framing error toler - ance bit 0 framing bit r a ng e bit 2 framing bit range bit 1 framing bit range bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 force re-synchroniza - tion r/w force re-synchronization: this read/write bit-field forces the re-synchronization pro - cess of the framer. when this bit is set to one: the framer started the re-synchronization process. after syn - chronization is achieved, the bit is automatically cleared. 6 synchronization with crc verification r/w synchronization with crc verification: this read/write bit-field forces the framer to obtain synchro - nization with crc verification. when this bit is set to zero: the framer obtains synchronization without crc match test. when this bit is set to one: crc match test is included as part of the synchronization pro - cess. b it n umber b it n ame b it t ype b it d escription txsigdl [2:0] national bits (sa4-sa8) timeslot 16 octet d or e timeslot 000 data link tscr txfrtd_n 001 data link txsig_n or txoh txfrtd_n 010 none txsig_n or txoh txfrtd_n 011 none txsig_n or txoh txfrtd_n 100 data link tscr txsig_n 101 reserved reserved reserved 110 reserved reserved reserved 111 reserved reserved reserved
xrt84l38 86 octal t1/e1/j1 framer rev. 1.0.1 5-3 framing error tolerance r/w framing error tolerance: these read/write bit-fields together with the range bits form the criteria for loss of frame alignment. in sf mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) or signaling framing bits (fs) are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in esf mode, a loss of frame alignment is typically declared if two out of four framing pattern sequence bits (fps) are incor - rect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in n mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in slc ? 96 mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) are incor - rect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in t1dm mode, a loss of frame alignment is typically declared if tolr out of rang bits are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. 2-0 framing bit range r/w framing bit range: these read/write bit-fields together with the tolerance bits form the criteria for loss of frame alignment. in sf mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) or signaling framing bits (fs) are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in esf mode, a loss of frame alignment is typically declared if two out of four framing pattern sequence bits (fps) are incor - rect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in n mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in slc ? 96 mode, a loss of frame alignment is typically declared if two out of four terminal framing bits (ft) are incor - rect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. in t1dm mode, a loss of frame alignment is typically declared if tolr out of rang bits are incorrect. therefore, the tolerance bits are normally set to two and the range bits are normally set to four. b it n umber b it n ame b it t ype b it d escription
xrt84l38 87 rev. 1.0.1 octal t1/e1/j1 framer framing control register (fcr) - e1 mode (indirect address = 0xn0h, 0x0bh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 force re- synchroniza - tion cas re-syn - chronization criteria bit 1 cas re-syn - chronization criteria bit 0 crc re- synchroniza - tion criteria bit 1 crc re- synchroniza - tion criteria bit 0 fas re-syn - chronization criteria bit 2 fas re-syn - chronization criteria bit 1 fas re-syn - chronization criteria bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 force re-synchroniza - tion r/w force re-synchronization: this read/write bit-field forces the re-synchronization pro - cess of the framer. when this bit is set to one: the framer started the re-synchronization process. after syn - chronization is achieved, the bit is automatically cleared. 6 - 5 cas re-synchronization criteria r/w cas re-synchronization criteria: these read/write bit-field determine the criteria of loss of cas multi-frame synchronization. when these bits are set to 00: two consecutive cas multi-frame alignment signal errors in the incoming frame will cause the declaration of loss of cas multi- frame synchronization. when these bits are set to 01: three consecutive cas multi-frame alignment signal errors in the incoming frame will cause the declaration of loss of cas multi-frame synchronization. when these bits are set to 10: four consecutive cas multi-frame alignment signal errors in the incoming frame will cause the declaration of loss of cas multi- frame synchronization. when these bits are set to 11: eight consecutive cas multi-frame alignment signal errors in the incoming frame will cause the declaration of loss of cas multi-frame synchronization.
xrt84l38 88 octal t1/e1/j1 framer rev. 1.0.1 4 - 3 crc re-synchronization criteria r/w crc re-synchronization criteria: these read/write bit-field determine the criteria of loss of crc multi-frame synchronization. when these bits are set to 00: if four consecutive crc multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of crc multi-frame synchronization. when these bits are set to 01: if two consecutive crc multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of crc multi-frame synchronization. when these bits are set to 10: if eight consecutive crc multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of crc multi-frame synchronization. when these bits are set to 11: if 915 or more consecutive crc multi-frame alignment signal errors in the incoming frames are detected in one second, the framer will declare loss of crc multi-frame synchronization. b it n umber b it n ame b it t ype b it d escription
xrt84l38 89 rev. 1.0.1 octal t1/e1/j1 framer 2 - 0 fas re-synchronization criteria r/w fas re-synchronization criteria: these read/write bit-field determine the criteria of loss of fas multi-frame synchronization. when these bits are set to 000: it is an illegal entry. the user should not set these bits to 000. when these bits are set to 001: if one fas multi-frame alignment signal error in the incoming frame is detected, the framer will declare loss of fas multi- frame synchronization. when these bits are set to 010: if two consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. when these bits are set to 011: if three consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. when these bits are set to 100: if four consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. when these bits are set to 101: if five consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. when these bits are set to 110: if six consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. when these bits are set to 111: if seven consecutive fas multi-frame alignment signal errors in the incoming frames are detected, the framer will declare loss of fas multi-frame synchronization. receive data link select register (rdlsr) - t1 mode (indirect address = 0xn0h, 0x0ch) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved receive data link bandwidth select bits [1:0] d/e timeslot destination select bits [1:0] data link destination select bits [1:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription
xrt84l38 90 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7-6 reserved x 5-4 receive data link band - width select r/w receive data link bandwidth select: these read/write bit-fields determined the bandwidth of facility data link channel of the framer when operating in esf mode. when these bits are set to 00: the facility data link is a 4khz channel. all available fdl bits (first bit of every other frame) are used as data link bits. when these bits are set to 01: the facility data link is a 2khz channel. only the odd fdl bits (first bit of frame 1, 5, 9?) are used as data link bits. when these bits are set to 10: the facility data link is a 2khz channel. only the even fdl bits (first bit of frame 3, 7, 11?) are used as data link bits.
xrt84l38 91 rev. 1.0.1 octal t1/e1/j1 framer 3-2 d/e timeslot source select r/w d/e timeslot source select: these read/write bit-fields permit the user to select data destination of d or e channel (d/e timeslot) for the isdn pri - mary rate interface. the isdn primary rate interface (isdn i.431) can carry b chan - nel, d channel, e channel and h channel. b channel has a bit rate of 64kbit/s and is equivalent to a ds0 channel in t1 used for payload transmission. d channel has a bit rate of 64kbit/s and is used primarily for signaling transmission. e channel has a bit rate of 64kbit/s and is used for signaling for circuit switching. it is used only with multiple-access configuration. h channel has bit rates of 384kbit/s, 1536kbit/s for t1 primary rate, and 1920kbit/s for e1 primary rate. the signaling information presented on d or e channels can be directed to several destinations. the user can send the signaling information to the receive serial data via the rxser_n pins. the user can also direct the signaling data to the receive lapd con - troller. the signaling information can be extracted from the receive lapd controller using microprocessor access. finally, the user can send the signaling information to fraction t1 output via the rxfrt1_n pins. when these bits are set to 00: the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive serial data output interface via the rxser_n pins. when these bits are set to 01: the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive hdlc controller. the user can read the receive lapd controller using microproces - sor access. when these bits are set to 10: the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive fractional t1 output interface via the rxfrt1_n pins. when these bits are set to 11: the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive serial data output interface via the rxser_n pins. b it n umber b it n ame b it t ype b it d escription
xrt84l38 92 octal t1/e1/j1 framer rev. 1.0.1 1-0 data link source select r/w data link source select: these read/write bit-fields permit the user to select data destination of the facility data link bits. the user can extract facility data link bits of the incoming data to the lapd controller or slca96 buffer. both lapd controller and slca96 buffer can be read through microprocessor access. the user can also direct received facility data link bits to receive serial data via rxser_n pins. overhead interface of the framer can also be used to output facility data link bits. finally, the user can force these data link bits to one. when these bits are set to 00: the facility data link bits of the incoming data stream are extracted to either the lapd controller or the slca96 buffer. the facility data link bits are also extracted into the receive serial data via the rxser pin. when these bits are set to 01: the facility data link bits of the incoming data stream are sent to the receive serial data output only. when these bits are set to 10: the facility data link bits of the incoming data stream are directed to the overhead interface via the rxoh_n pins. the facility data link bits are also extracted into the receive serial data via the rxser pin. when these bits are set to 11: the facility data link bits of the incoming data stream are forced to one by the framer and are outputted to the receive serial data output. receive data link select register (rdlsr) - e1 mode(indirect address = 0xn0h, 0x0ch) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa8 data link select receive sa8 data link select receive sa8 data link select receive sa8 data link select receive sa8 data link select receive signaling and data link select bits [2:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 receive sa8 data link select r/w receive sa8 data link select: this read/write bit-field permit the user to select data desti - nation of the sa8 national bit. when this bit is set to 0: destination of the sa8 national bit is not the data link interface. when this bit is set to 1: destination of the sa8 national bit is the data link interface. b it n umber b it n ame b it t ype b it d escription
xrt84l38 93 rev. 1.0.1 octal t1/e1/j1 framer 6 receive sa7 data link select r/w receive sa7 data link select: this read/write bit-field permit the user to select data desti - nation of the sa7 national bit. when this bit is set to 0: destination of the sa7 national bit is not the data link interface. when this bit is set to 1: destination of the sa7 national bit is the data link interface. 5 receive sa6 data link select r/w receive sa6 data link select: this read/write bit-field permit the user to select data desti - nation of the sa6 national bit. when this bit is set to 0: destination of the sa6 national bit is not the data link interface. when this bit is set to 1: destination of the sa6 national bit is the data link interface. 4 receive sa5 data link select r/w receive sa5 data link select: this read/write bit-field permit the user to select data desti - nation of the sa5 national bit. when this bit is set to 0: destination of the sa5 national bit is not the data link interface. when this bit is set to 1: destination of the sa5 national bit is the data link interface. 3 receive sa4 data link select r/w receive sa4 data link select: this read/write bit-field permit the user to select data desti - nation of the sa4 national bit. when this bit is set to 0: destination of the sa4 national bit is not the data link interface. when this bit is set to 1: destination of the sa4 national bit is the data link interface. b it n umber b it n ame b it t ype b it d escription
xrt84l38 94 octal t1/e1/j1 framer rev. 1.0.1 2-0 receive signaling and data link select r/w receive signaling and data link select: these read/write bit-fields permit the user to select data destination of the national bits, the timeslot 16 octet as well as the d or e time slot. national bits when these bits are set to 000: the data link interface is destination of the sa4 through sa8 nation bits, if the corresponding receive sa data link select bit(s) (bit 3 to bit 7 of the receive signaling and data link select register) are set to 1. when these bits are set to 001: the data link interface is destination of the sa4 through sa8 nation bits, if the corresponding receive sa data link select bit(s) (bit 3 to bit 7 of the receive signaling and data link select register) are set to 1. when these bits are set to 010: the sa4 through sa8 nation bits are forced to 1.when these bits are set to 011:the sa4 through sa8 nation bits are forced to 1. when these bits are set to 100: the data link interface is destination of the sa4 through sa8 nation bits, if the corresponding receive sa data link select bit(s) (bit 3 to bit 7 of the receive signaling and data link select register) are set to 1. when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved. timeslot 16 octet when these bits are set to 000: timeslot 16 octet is taken directly from the pcm data which in term determines by the receive channel control register (rccr). when these bits are set to 001: timeslot 16 octet is output by the receive overhead input inter - face through the rxoh_n pin or by the receive signaling serial interface through the rxsig_n pin. the receive signaling regis - ter array (rsra) of each timeslot stores its correspondent timeslot 16 octet as well. when these bits are set to 010: timeslot 16 octet is output by the receive overhead input inter - face through the rxoh_n pin or by the receive signaling serial interface through the rxsig_n pin. the receive signaling regis - ter array (rsra) of each timeslot stores its correspondent timeslot 16 octet as well. when these bits are set to 011: timeslot 16 octet is output by the receive overhead input inter - face through the rxoh_n pin or by the receive signaling serial interface through the rxsig_n pin. the receive signaling regis - ter array (rsra) of each timeslot stores its correspondent timeslot 16 octet as well. b it n umber b it n ame b it t ype b it d escription
xrt84l38 95 rev. 1.0.1 octal t1/e1/j1 framer when these bits are set to 100: timeslot 16 octet is taken directly from the pcm data which in term determines by the receive channel control register (rccr). when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved.d/e time slot when these bits are set to 000: d or e time slot data are output through the receive fractional data input interface (rxfrtd_n pin). when these bits are set to 001: d or e time slot data are output through the receive fractional data input interface (rxfrtd_n pin). when these bits are set to 010: d or e time slot data are output through the receive fractional data input interface (rxfrtd_n pin). when these bits are set to 011: d or e time slot data are output through the receive fractional data input interface (rxfrtd_n pin). when these bits are set to 100: d or e time slot data are output through the receive serial sig - naling input interface (rxsig_n pin). when these bits are set to 101: reserved. when these bits are set to 110: reserved. when these bits are set to 111: reserved. the following table summaries destinations of national bits, timeslot 16 octet and d or e time slots. b it n umber b it n ame b it t ype b it d escription rxsigdl[2:0] national bits (sa4-sa8) timeslot 16 octet d or e timeslot 000 data link rccr rxfrtd_n 001 data link rxsig_n or rxoh rxfrtd_n 010 none rxsig_n or rxoh rxfrtd_n 011 none rxsig_n or rxoh rxfrtd_n 100 data link rccr rxsig_n 101 reserved reserved reserved 110 reserved reserved reserved 111 reserved reserved reserved
xrt84l38 96 octal t1/e1/j1 framer rev. 1.0.1 signaling change register 0 (scr0) (indirect address = 0xn0h, 0x0dh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling change bit of channel 0 signaling change bit of channel 1 signaling change bit of channel 2 signaling change bit of channel 3 signaling change bit of channel 4 signaling change bit of channel 5 signaling change bit of channel 6 signaling change bit of channel 7 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 signaling change indication rur signaling change indication: these reset upon read bit-fields indicate whether the signaling data associated with channel 0-7 has changed since the last read of this register. when these bits are zero: signaling data associated with certain channel has not changed since last read of the register. when these bits are one: signaling data associated with certain channel has changed since last read of the register. signaling change register 1 (scr0) (indirect address = 0xn0h, 0x0eh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling change bit of channel 8 signaling change bit of channel 9 signaling change bit of channel 10 signaling change bit of channel 11 signaling change bit of channel 12 signaling change bit of channel 13 signaling change bit of channel 14 signaling change bit of channel 15 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 signaling change indication rur signaling change indication: these reset upon read bit-fields indicate whether the signaling data associated with channel 8-15 has changed since the last read of this register. when these bits are zero: signaling data associated with certain channel has not changed since last read of the register. when these bits are one: signaling data associated with certain channel has changed since last read of the register.
xrt84l38 97 rev. 1.0.1 octal t1/e1/j1 framer signaling change register 2 (scr2) (indirect address = 0xn0h, 0x0fh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling change bit of channel 16 signaling change bit of channel 17 signaling change bit of channel 18 signaling change bit of channel 19 signaling change bit of channel 20 signaling change bit of channel 21 signaling change bit of channel 22 signaling change bit of channel 23 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 signaling change indication rur signaling change indication: these reset upon read bit-fields indicate whether the signaling data associated with channel 16-23 has changed since the last read of this register. when these bits are zero: signaling data associated with certain channel has not changed since last read of the register. when these bits are one: signaling data associated with certain channel has changed since last read of the register. signaling change register 3 (scr3) - e1 mode only (indirect address = 0xn0h, 0x10h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling change bit of channel 24 signaling change bit of channel 25 signaling change bit of channel 26 signaling change bit of channel 27 signaling change bit of channel 28 signaling change bit of channel 29 signaling change bit of channel 30 signaling change bit of channel 31 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 signaling change indication rur signaling change indication: these reset upon read bit-fields indicate whether the signaling data associated with channel 24-31 has changed since the last read of this register. when these bits are zero: signaling data associated with certain channel has not changed since last read of the register. when these bits are one: signaling data associated with certain channel has changed since last read of the register.
xrt84l38 98 octal t1/e1/j1 framer rev. 1.0.1 receive national bits register (rnbr) - e1 mode only (indirect address = 0xn0h, 0x11h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 international bit in fas frame international bit in non- fas frame remote alarm indi - cation bit national bit sa4 national bit sa3 national bit sa2 national bit sa1 national bit sa0 r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 international bit in fas frame r/o international bit in fas frame: this read-only bit-field corresponds to the value contained in the international bit of received fas frame. 6 international bit in non- fas frame r/o international bit in non-fas frame: this read-only bit-field corresponds to the value contained in the international bit of received non-fas frame. 5 remote alarm indication bit r/o remote alarm indication bit: this read-only bit-field corresponds to the value contained in the remote alarm indication (frame yellow alarm) bit position of the received non-fas frame. 4 national bit sa4 r/o national bit sa4: this read-only bit-field corresponds to the value contained in the national bit sa4 position of the received non-fas frame. 3 national bit sa5 r/o national bit sa5: this read-only bit-field corresponds to the value contained in the national bit sa4 position of the received non-fas frame. 2 national bit sa6 r/o national bit sa6: this read-only bit-field corresponds to the value contained in the national bit sa4 position of the received non-fas frame. 1 national bit sa7 r/o national bit sa7: this read-only bit-field corresponds to the value contained in the national bit sa4 position of the received non-fas frame. 0 national bit sa8 r/o national bit sa8: this read-only bit-field corresponds to the value contained in the national bit sa4 position of the received non-fas frame.
xrt84l38 99 rev. 1.0.1 octal t1/e1/j1 framer receive extra bits register (rebr) - e1 mode only (indirect address = 0xn0h, 0x12h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved extra bit 1 far-end remote alarm indi - cation bit extra bit 2 extra bit 3 r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 - 4 reserved r/o 3 extra bit 1 r/o extra bit 1: this read-only bit-field corresponds to the value contained in the extra bit 1 position (bit 5 in timeslot 16 of frame 0 of the cas multi-frame) of the received e1 data. 2 far-end remote alarm indication bit r/o far-end remote alarm indication bit: this read-only bit-field corresponds to the value contained in the far-end remote alarm indication (cas multi-frame yellow alarm) bit position (bit 6 in timeslot 16 of frame 0 of the cas multi-frame) of the received non-fas frame. 1 extra bit 2 r/o extra bit 2: this read-only bit-field corresponds to the value contained in the extra bit 2 position (bit 7 in timeslot 16 of frame 0 of the cas multi-frame) of the received e1 data. 0 extra bit 3 r/o extra bit 3: this read-only bit-field corresponds to the value contained in the extra bit 3 position (bit 8 in timeslot 16 of frame 0 of the cas multi-frame) of the received e1 data. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 slca96 enable mos abort enable receive fcs verifi - cation enable automatic receive lapd message transmit abort sequence transmit idle/flag sequence transmit lapd message with fcs mos or bos select r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt84l38 100 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7 slc ? 96 enable r/w slc ? 96 enable: this read/write bit-field permits the user to enable slc ? 96 data link transmission in slc ? 96 framing mode. in esf framing mode, this read/write bit-field allows facility data link of the framer to transmit and receive slc ? 96-like message. when this bit is set to zero: in slc ? 96 framing mode, the slc ? 96 data link transmission is disabled. the framer transmits terminal framing bits as in sf framing mode. the signaling framing bits are forced to ones. in esf framing mode, facility data link of the framer is config - ured to transmit and receive regular data link message. when this bit is set to one: in slc ? 96 framing mode, the slc ? 96 data link transmission is enabled. the framer transmits terminal framing bits as in sf framing mode. the signaling framing bits are transmitted and received in slc ? 96 data link format. in esf framing mode, facility data link of the framer is config - ured to transmit and receive slc ? 96-like message. 6 mos abort enable r/w mos abort enable: this read/write bit-field enables and disables the transmit lapd controller of the framer to automatically insert an abort sequence anytime it transitions from the message oriented sig - naling (mos) mode to the bit oriented signaling (bos) mode. when this bit is set to zero: the transmit lapd controller inserts an mos abort sequence to the data link message when the framer transitions from mos to bos. when this bit is set to one: the transmit lapd controller does not insert an mos abort sequence to the data link message when the framer transitions from mos to bos. 5 receive fcs verification enable r/w receive fcs verification enable: this read/write bit-field enables and disables the receive lapd controller of the framer to compute and verify the frame check sequence (fcs) value in the incoming lapd message. when this bit is set to zero: the receive lapd controller computes and verifies the frame check sequence (fcs) of each mos message. when this bit is set to one: the receive lapd controller does not compute and verify the frame check sequence (fcs) of each mos message.
xrt84l38 101 rev. 1.0.1 octal t1/e1/j1 framer 4 automatic receive lapd message r/w automatic receive lapd message: this read/write bit-field configures the receive lapd con - troller of the framer to compare and discard any incoming lapd message that exactly match which is currently stored in the receive lapd controller. when this bit is set to zero: the receive lapd controller does not discard any incoming lapd message. every incoming lapd message automatically stores in the receive lapd controller and overwrites the previ - ous received lapd message. when this bit is set to one: the receive lapd controller compares any incoming lapd message with the previous message that is currently stored in the received lapd controller. if the incoming lapd message is the same as the previous one, it will be automatically discarded. 3 transmit abort sequence r/w transmit abort sequence: this read/write bit-field configures the transmit lapd con - troller to transmit an abort sequence into the facility data link channel to the remote terminal. an abort sequence is a string of seven or more consecutive ones. when this bit is set to zero: the transmit lapd controller does not insert an abort sequence into the facility data link channel. when this bit is set to one: the transmit lapd controller inserts an abort sequence into the facility data link channel. 2 transmit idle/flag sequence r/w transmit idle/flag sequence: this read/write bit-field configures the transmit lapd con - troller to insert a string of idle/flag sequence into the facility data link channel to the remote terminal. an idle/flag sequence is an octet of with value 0x7e. when this bit is set to zero: the transmit lapd controller does not insert an idle/flag sequence into the facility data link channel. when this bit is set to one: the transmit lapd controller inserts an idle/flag sequence into the facility data link channel. 1 transmit lapd message with fcs r/w transmit lapd message with fcs: this read/write bit-field forces the transmit lapd controller to include frame check sequence (fcs) octets into the out - bound lapd message. when this bit is set to zero: the transmit lapd controller does not include fcs octets into the outbound lapd message. when this bit is set to one: the transmit lapd controller inserts fcs octets into the out - bound lapd message. n ote : this bit-field is ignored if the framer is configured to operate in bos mode. b it n umber b it n ame b it t ype b it d escription
xrt84l38 102 octal t1/e1/j1 framer rev. 1.0.1 0 mos or bos select r/w mos or bos select: this read/write bit-field specifies whether the transmit and receive lapd controller to operate in message oriented sig - naling (mos) or bit oriented signaling (bos) mode. when this bit is set to zero: the transmit and receive lapd controller transmit and receive lapd message in mos mode. when this bit is set to one: the transmit and receive lapd controller transmit and receive lapd message in bos mode. transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit data link buffer select transmit data link byte count bits [6:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 transmit data link buffer select r/w transmit data link buffer select: this read/write bit-field permits the user to select which one of the two transmit data link buffers will be loaded for transmis - sion. when this bit is set to zero: the transmit data link buffer 0 will be loaded for transmission of data link bits. when this bit is set to one: the transmit data link buffer 1 will be loaded for transmission of data link bits. b it n umber b it n ame b it t ype b it d escription
xrt84l38 103 rev. 1.0.1 octal t1/e1/j1 framer 6 - 0 transmit data link byte count [6:0] r/w transmit data link byte count [6:0]: these read/write bit-fields hold the length of the mos mes - sage to be transmitted or the number of repetitions of bos to be transmitted. the user should program these bit-fields to equal the length of the mos message in bytes or the number of repeti - tions of bos message. the lapd controller will load the value of these bits from the transmit data link byte count register and use it as its internal counter at the beginning of each transfer. after the entire mos message is transmitted or x number of repetitions of bos mes - sage transmission is completed, the lapd controller will gener - ate the transmit end of transfer (txeot) interrupt. each transmit data link buffer is 96-bytes wide. n ote : in the case of bos messaging, if these bit-fields are equal to zero, the bos message will be transmitted infinitely and no transmit end of transfer (txeot) interrupt will be generated. receive data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x15h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive data link buffer select receive data link byte count bits [6:0] r r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 receive data link buffer select r receive data link buffer select: this read/write bit-field informs the user which one of the two receive data link buffers are available for receiving data link messages. when this bit is set to zero: the receive data link buffer 0 will be used for received data link bits. when this bit is set to one: the receive data link buffer 1 will be used for received data link bits. b it n umber b it n ame b it t ype b it d escription
xrt84l38 104 octal t1/e1/j1 framer rev. 1.0.1 6 - 0 receive data link byte count [6:0] r/w receive data link byte count [6:0]: these read/write bit-fields hold the length of the mos mes - sage received or the number of repetitions of bos message received. the user should program these bit-fields to equal the length of the mos message in bytes or the number of repetitions of bos message. the lapd controller will load the value of these bits from the receive data link byte count register and use it as its internal counter at the beginning of each transfer. after the entire mos message is received or x number of repetitions of bos message is received, the lapd controller will generate the receive end of transfer (rxeot) interrupt. each receive data link buffer is 96-bytes wide. n ote : in the case of bos messaging, these bit-fields cannot be set to zero. otherwise, no receive end of transfer (rxeot) interrupt will be generated. slip buffer control register (sbcr) (indirect address = 0xn0h, 0x16h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit slip buffer is fifo reserved force signaling freeze signaling freeze enable slip buffer receive synchroniza - tion direction slip buffer enable bit [1:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 transmit slip buffer is fifo r/w slip buffer is fifo: this read/write bit-field allows the user to determine function of the buffer when txlineclk_n and txserclk_n are synchro - nized with each other. when this bit is 0: the buffer acts as slip buffer if enabled by the slip buffer enable bit [1:0]. when this bit is 1: the buffer acts as fifo. 6 - 5 reserved b it n umber b it n ame b it t ype b it d escription
xrt84l38 105 rev. 1.0.1 octal t1/e1/j1 framer 4 force signaling freeze r/w force signaling freeze: this read/write bit-field allows the user to stop further signal - ing updating. when this bit is 0: the framer continues extracts and updates signaling information received. when this bit is 1: the framer stops extracting signaling information received, this is called signaling freeze. 3 signaling freeze enable r/w signaling freeze enable: this read/write allows the user to stop the framer from updating signaling information for one multi-frame after buffer slipping. enabling signaling freeze after buffer slipping can elimi - nate incorrect signaling information been extracted and updated by the framer. when this bit is 0: signaling freeze is disabled. the framer will continue to extract and update signaling information for one multi-framer after buffer slipping. when this bit is 1: signaling freeze is enabled. the framer will not extract and update signaling information for one multi-framer after buffer slipping. 2 slip buffer receive syn - chronization direction r/w slip buffer receive synchronization direction: when this bit is set to 0: the receive single-frame synchronization signal (rxsync_n) is an output if the slip buffer is not in bypass mode. when this bit is set to 1: the receive single-frame synchronization signal (rxsync_n) is an input if the slip buffer is not in bypass mode. b it n umber b it n ame b it t ype b it d escription
xrt84l38 106 octal t1/e1/j1 framer rev. 1.0.1 1-0 slip buffer enable r/w slip buffer enable: when these bits are set to 00: slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output. when these bits are set to 01: the elastic store (slip buffer) is enabled. the receive payload data is passing from the receive framer module through the slip buffer to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. when these bits are set to 10: the slip buffer acts as a fifo. the fifo latency register (flr) determines the data latency. the receive payload data is passing from the receive framer module through the fifo to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. when these bits are set to 11: slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output. fifo latency register (fifolr) (indirect address = 0xn0h, 0x17h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved fifo latency [4:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-5 reserved r/w 4-0 fifo latency r/w fifo latency: these bits determine depth of the fifo in terms of bytes. the largest possible value is thirty-two bytes or one e1 frame. b it n umber b it n ame b it t ype b it d escription
xrt84l38 107 rev. 1.0.1 octal t1/e1/j1 framer interrupt control register (icr) (indirect address = 0xn0h, 0x1ah) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved clear interrupt status bits by write clear interrupt enable bits enable of interrupt generation r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-3 reserved r/w 2 clear interrupt status bits by write r/w clear interrupt status bit by write: this read/write bit field determines how to clear the interrupt sta - tus bits. when this bit is set to 0: the status bits are reset upon read. when this bit is set to 1: the status bits are reset by writing a zero. 1 clear interrupt enable bits r/w clear interrupt enable bit: this read/write bit field determines how to clear the interrupt enable bits. when this bit is set to 0: the status bits are not reset upon reading of corresponding sta - tus bits. when this bit is set to 1: the status bits are reset upon reading of corresponding status bits. 0 enable of interrupt generation r/w enable of interrupt generation: this read/write bit field is used to enable t1/e1 framer interrupt generation. when this bit is set to 0: xrt84l38 will not generate interrupt. instead, status polling of the framer will be enabled. when this bit is set to 1: interrupt generation is enabled.
xrt84l38 108 octal t1/e1/j1 framer rev. 1.0.1 lapd channel select register (lcsr) (indirect address = 0xn0h, 0x1bh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved lapd channel select bit [1:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-2 reserved r/w 1-0 lapd channel select bit [1:0] r/w lapd channel select bit [1:0]: these read/write bit fields determine which one of the three current lapd channel being accessed. when these bits are set to 00: lapd channel 1 is being accessed. when these bits are set to 01: lapd channel 2 is being accessed. when these bits are set to 10: lapd channel 3 is being accessed. when these bits are set to 11: lapd channel 1 is being accessed. transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit fraction data inter - face select reserved transmit payload clock select / transmit sync- pulse low active select transmit fractional e1 input enable transmit clock inversion transmit multiplex enable transmit interface mode select bit 1 transmit interface mode select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt84l38 109 rev. 1.0.1 octal t1/e1/j1 framer b it n umber b it n ame b it t ype b it d escription 7 transmit fraction data interface select r/w transmit fraction data interface select: when this bit is set to 0: the transmit serial fractional data (txfrtd_n) input pins are used to accept fractional serial data. the transmit timeslot clock (txtsclk_n) pins are used to output fractional data clock. when this bit is set to 1: the transmit timeslot clock (txtsclk_n) pins are used to input fractional serial data enable signal. fractional serial data is clocked into the framer using ungapped txserclk_n signals. 6 reserved 5 transmit payload clock select / transmit sync- pulse low active select r/w transmit payload clock select / transmit sync- pulse low active select: when this bit is set to 0: the txserclk_n pins will output ungapped transmit clock for correspondent ds1/e1 clock rates. in non-1.544 mhz mode for ds1 or non-2.048 mhz mode for e1, the xrt84l38 chip expects a high active pulse for frame syn - chronization. when this bit is set to 1: the txserclk_n pins will output a gapped transmit clock with oh bit period blocked for correspondent ds1/e1 clock rates. in non-1.544 mhz mode for ds1 or non-2.048 mhz mode for e1, the xrt84l38 chip expects a low active pulse for frame syn - chronization.
xrt84l38 110 octal t1/e1/j1 framer rev. 1.0.1 4 transmit fractional e1 input enable r/w transmit fractional e1 input enable: when this bit is set to 0: the transmit time-slot indication bits (txtsb[4:0] are outputting five-bit binary values of time-slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. the transmit time-slot indicator clock signal (txtsclk_n) is a 256khz clock that pulses high for one e1 bit period whenever the transmit payload data input interface block is accepting the lsb of each of the twenty-four time slots. when this bit is set to 1: the txtsb[0]_n bit becomes the transmit fractional e1 input signal (txfrtd_n) which carries fractional e1 payload data into the framer. the txtsb[1]_n bit becomes the transmit signaling data input signal (txsig_n) which is used to insert robbed-bit signaling data into the outbound e1 frame. the txtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. the txtsb[3]_n bit becomes the transmit overhead synchroni - zation pulse (txohsync_n) which is used to output an over - head synchronization pulse that indicates the first bit of each e1multi-frame. the txtsclk_n will output gaped fractional e1 clock that can be used by terminal equipment to clock out fractional e1 payload data at rising edge of the clock. or, the txtsclk_n pin will be a clock enable signal to transmit fractional e1 input signal (txfrtd_n) when the un-gaped transmit serail input clock (txserclk_n) is used to clock in fractional e1 payload data into the framer. 3 transmit clock inversion r/w transmit clock inversion: when this bit is set to 0: serial data transition happens on rising edge of the transmit serial clock. when this bit is set to 1: serial data transition happens on falling edge of the transmit serial clock. 2 transmit multiplex enable r/w transmit multiplex enable: when this bit is set to 0: the transmit back-plane interface block is configured to non- channel-multiplexed mode when this bit is set to 1: the transmit back-plane interface block is configured to chan - nel-multiplexed mode b it n umber b it n ame b it t ype b it d escription
xrt84l38 111 rev. 1.0.1 octal t1/e1/j1 framer 1-0 transmit interface mode select r/w transmit interface mode select: when combined with the transmit multiplex enable bit, these bits determine the transmit back-plane interface data rate. the table below illustrates the transmit back-plane interface data rate for e1 mode with different transmit multiplex enable bit and transmit interface mode select bits settings. receive interface control register (ri cr) (indirect address = 0xn0h, 0x22h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive fraction data inter - face select reserved receive payload clock select / receive sync- pulse low active select receive fractional e1 input enable receive clock inversion receive multiplex enable receive interface mode select bit 1 receive interface mode select bit 0 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 0 0 xrt84v24 compatible 2.048mbit/s 1 0 4.096mbit/s 1 1 8.192mbit/s 0 0 - 0 1 bit multiplexed 16.384mbit/s 1 0 hmvip 16.384mbit/s 1 1 h.100 16.384mbit/s transmit interface mode select bit 1 transmit interface mode select bit 0 back-plane interface data rate 0 0 0 1 1 1 1 transmit multiplex enable bit 0 1 mvip 2.048mbit/s 0
xrt84l38 112 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7 receive fraction data interface select r/w receive fraction data interface select: when this bit is set to 0: the receive serial fractional data (rxfrtd_n) output pins are used to output fractional serial data. the receive timeslot clock (rxtsclk_n) pins are used to output fractional data clock. when this bit is set to 1: the receive timeslot clock (rxtsclk_n) pins are used to out - put fractional serial data enable signal. fractional serial data is clocked out from the framer using ungapped rxserclk_n signals. 6 reserved 5 receive payload clock select / receive sync- pulse low active select r/w receive payload clock select / receive sync- pulse low active select: when this bit is set to 0: the rxserclk_n pins will output ungapped receive clock for correspondent ds1/e1 clock rates. in non-1.544 mhz mode for ds1 or non-2.048 mhz mode for e1, the xrt84l38 chip generates a high active pulse for frame synchronization. when this bit is set to 1: the rxserclk_n pins will output a gapped receive clock with oh bit period blocked for correspondent ds1/e1 clock rates. in non-1.544 mhz mode for ds1 or non-2.048 mhz mode for e1, the xrt84l38 chip generates a low active pulse for frame syn - chronization.
xrt84l38 113 rev. 1.0.1 octal t1/e1/j1 framer 4 receive fractional e1 output enable r/w receive fractional e1 output enable: when this bit is set to 0: the receive time-slot indication bits (rxtsb[4:0] are outputting five-bit binary values of time-slot number (0-31) being accepted and processed by the receive payload data output interface block of the framer. the receive time-slot indicator clock signal (rxtsclk_n) is a 256khz clock that pulses high for one e1 bit period whenever the receive payload data output interface block is accepting the lsb of each of the twenty-four time slots. when this bit is set to 1: the rxtsb[0]_n bit becomes the receive fractional e1 output signal (rxfrtd_n) which carries fractional e1 payload data from the framer. the rxtsb[1]_n bit becomes the receive signaling data output signal (rxsig_n) which is used to carry robbed-bit signaling data extracted from the inbound e1 frame. the rxtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-31) being accepted and processed by the receive payload data output interface block of the framer. the rxtsclk_n will output gaped fractional e1 clock that can be used by terminal equipment to latch in fractional e1 payload data at rising edge of the clock. or, the rxtsclk_n pin will be a clock enable signal to receive fractional e1 output signal (rxfrtd_n) when the un-gaped receive serail output clock (rxserclk_n) is used to latch in fractional e1 payload data into the terminal equipment. 3 receive clock inversion r/w receive clock inversion: when this bit is set to 0: serial data transition happens on rising edge of the receive serial clock. when this bit is set to 1: serial data transition happens on falling edge of the receive serial clock. 2 receive multiplex enable r/w receive multiplex enable: when this bit is set to 0: the receive back-plane interface block is configured to non- channel-multiplexed mode. when this bit is set to 1: the receive back-plane interface block is configured to chan - nel-multiplexed mode b it n umber b it n ame b it t ype b it d escription
xrt84l38 114 octal t1/e1/j1 framer rev. 1.0.1 1-0 receive interface mode select r/w receive interface mode select: when combined with the receive multiplex enable bit, these bits determine the receive back-plane interface data rate. the table below illustrates the receive back-plane interface data rate for e1 mode with different receive multiplex enable bit and receive interface mode select bits settings. general test register (gtr) (indirect address = 0xn0h, 0x23h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 prbs type select error insertion data inversion select receive prbs lock indication receive prbs block enable transmit prbs block enable receive ds1/e1 framer bypassed transmit ds1/e1 framer bypassed r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 prbs type select r/w prbs type select: when this bit is set to 0: the polynomial for generating the prbs pattern is x15 + x14 + 1. when this bit is set to 1: a qrts pattern is generated as the prbs pattern. b it n umber b it n ame b it t ype b it d escription 0 0 xrt84v24 compatible 2.048mbit/s 1 0 4.096mbit/s 1 1 8.192mbit/s 0 0 - 0 1 bit multiplexed 16.384mbit/s 1 0 hmvip 16.384mbit/s 1 1 h.100 16.384mbit/s receive interface mode select bit 1 receive interface mode select bit 0 back-plane interface data rate 0 0 0 1 1 1 1 receive multiplex enable bit 0 1 mvip 2.048mbit/s 0
xrt84l38 115 rev. 1.0.1 octal t1/e1/j1 framer 6 error insertion r/w error insertion: a zero to one transition of this bit will cause one bit of the outgo - ing transmit data inverted. 5 data inversion select r/w data inversion select: when this bit is set to 0: the outgoing transmit data and incoming receive data are not changed. when this bit is set to 1: the outgoing transmit data and incoming receive data are inverted. 4 receive prbs lock indication r/w receive prbs lock indication: if the receive prbs block is enabled, this bit indicates whether a prbs pattern is found in the incoming received data and the prbs pattern is locked. when this bit is set to 0: there is no prbs pattern found and locked in the incoming received data stream. when this bit is set to 1: a prbs pattern found and locked in the incoming received data stream. 3 receive prbs block enable r/w receive prbs block enable : when this bit is set to 0: the receive prbs block is disabled. the framer will not check the incoming received data for prbs pattern. when this bit is set to 1: the receive prbs block is enabled. the framer will check the incoming received data for prbs pattern. 2 transmit prbs block enable r/w transmit prbs block enable : when this bit is set to 0: the transmit prbs block is disabled. the framer will not insert prbs pattern into the outgoing transmit data stream. when this bit is set to 1: the transmit prbs block is enabled. the framer will insert prbs pattern into the outgoing transmit data stream. 1 receive ds1/e1 framer bypassed r/w receive ds1/e1 framer bypassed: when this bit is set to 0: the receive ds1/e1 framer is not bypassed. when this bit is set to 1: the receive ds1/e1 framer is bypassed. 0 transmit ds1/e1 framer bypassed r/w transmit ds1/e1 framer bypassed: when this bit is set to 0: the transmit ds1/e1 framer is not bypassed. when this bit is set to 1: the transmit ds1/e1 framer is bypassed. unframed ds1/e1 payload data are passed from backplane interface into the ds1/ e1 line. b it n umber b it n ame b it t ype b it d escription
xrt84l38 116 octal t1/e1/j1 framer rev. 1.0.1 loop-back code control register (lccr) (indirect address = 0xn0h, 0x24h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive loop-back code activation length bit 1 receive loop-back c o de activation length bit 0 receive loop-back code de-activa - tion length bit 1 receive loop-back code de-activa - tion length bit 0 transmit loop-back code length bit 1 transmit loop-back code length bit 0 framed loop-back code select automatic loop-back select r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-6 receive loop-back code activation length r/w receive loop-back code activation length: these bits are used to determine the receive loop-back code activation length. the table below shows length of the receive loop-back activation code according to values of these bits. 5-4 receive loop-back code de-activation length r/w receive loop-back code activation length: these bits are used to determine the receive loop-back code de-activation length. the table below shows length of the receive loop-back de-activation code according to values of these bits. bit value 00 01 10 11 length of loop-back code 4 5 6 7 bit value 00 01 10 11 length of loop-back code 4 5 6 7
xrt84l38 117 rev. 1.0.1 octal t1/e1/j1 framer 3-2 transmit loop-back code length r/w transmit loop-back code length: these bits are used to determine the transmit loop-back code activation length. the table below shows length of the transmit loop-back code according to values of these bits. 1 framed loop-back code select r/w framed loop-back code select: when this bit is set to 0: the loop-back code that transmitted or recieved is unframed. when this bit is set to 1: the loop-back code that transmitted or received is framed. 0 automatic loop-back select r/w automatic loop-back select: when this bit is set to 0: automatic loop-back is disabled. when this bit is set to 1: automatic loop-back is enabled. transmit loop-back code register (tlcr) (indirect address = 0xn0h, 0x25h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit loop-back code bit[6:0] transmit loop-back code enable r/w r/w r/w r/w r/w r/w r/w r/w 1 0 1 0 1 0 1 0 b it n umber b it n ame b it t ype b it d escription 7-1 transmit loop-back code bit[6:0] r/w transmit loop-back code bit[6:0]: these bits are the transmit loop-back code sequence. b it n umber b it n ame b it t ype b it d escription bit value 00 01 10 11 length of loop-back code 4 5 6 7
xrt84l38 118 octal t1/e1/j1 framer rev. 1.0.1 0 transmit loop-back code enable r/w transmit loop-back code enable: when this bit is set to 0: transmit loop-back code is disabled. transmit loop-back code is not sent to the line. when this bit is set to 1: transmit loop-back code is enabled. transmit loop-back code is generated and repeatedly sent to the line instead of payload data. receive loop-back activation code register (rlacr) (indirect address = 0xn0h, 0x26h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive loop-back activation code bit[6:0] receive loop-back activation code enable r/w r/w r/w r/w r/w r/w r/w r/w 1 0 1 0 1 0 1 0 b it n umber b it n ame b it t ype b it d escription 7-1 receive loop-back activation code bit[6:0] r/w receive loop-back activation code bit[6:0]: these bits are the receive loop-back activation code sequence. 0 receive loop-back activation code enable r/w receive loop-back activation code enable: when this bit is set to 0: receive loop-back activation code is disabled. receive loop- back activation code is not sent to the line. when this bit is set to 1: receive loop-back activation code is enabled. receive loop- back activation code is generated and repeatedly sent to the line instead of payload data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 119 rev. 1.0.1 octal t1/e1/j1 framer receive loop-back de-activation code register (rlacr) (indirect address = 0xn0h, 0x27h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive loop-back de-activation code bit[6:0] receive loop-back de-activa - tion code enable r/w r/w r/w r/w r/w r/w r/w r/w 1 0 1 0 1 0 1 0 b it n umber b it n ame b it t ype b it d escription 7-1 receive loop-back de-activation code bit[6:0] r/w receive loop-back de-activation code bit[6:0]: these bits are the receive loop-back de-activation code sequence. 0 receive loop-back de-activation code enable r/w receive loop-back de-activation code enable: when this bit is set to 0: receive loop-back de-activation code is disabled. receive loop-back de-activation code is not sent to the line. when this bit is set to 1: receive loop-back de-activation code is enabled. receive loop-back de-activation code is generated and repeatedly sent to the line instead of payload data. transmit sa select register (tsasr) (indirect address = 0xn0h, 0x030h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa8 select transmit sa7 select transmit sa6 select transmit sa5 select transmit sa4 select loop-back mode 1 auto enable loop-back mode 2 auto enable loop-back release auto enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 transmit sa8 select r/w transmit sa8 select: this bit determines whether the source of sa8 bit is from trans - mit serial input or transmit sa8 register. when this bit is set to 0: the source of .sa8 bit is from transmit serial input. when this bit is set to 1: the source of .sa8 bit is from transmit sa8 register.
xrt84l38 120 octal t1/e1/j1 framer rev. 1.0.1 6 transmit sa7 select r/w transmit sa7 select: this bit determines whether the source of sa7 bit is from trans - mit serial input or transmit sa7 register. when this bit is set to 0: the source of .sa7 bit is from transmit serial input. when this bit is set to 1: the source of .sa7 bit is from transmit sa7 register. 5 transmit sa6 select r/w transmit sa6 select: this bit determines whether the source of sa6 bit is from trans - mit serial input or transmit sa6 register. when this bit is set to 0: the source of .sa6 bit is from transmit serial input. when this bit is set to 1: the source of .sa6 bit is from transmit sa6 register. 4 transmit sa5 select r/w transmit sa5 select: this bit determines whether the source of sa5 bit is from trans - mit serial input or transmit sa5 register. when this bit is set to 0: the source of .sa5 bit is from transmit serial input. when this bit is set to 1: the source of .sa5 bit is from transmit sa5 register. 3 transmit sa4 select r/w transmit sa4 select: this bit determines whether the source of sa4 bit is from trans - mit serial input or transmit sa4 register. when this bit is set to 0: the source of .sa4 bit is from transmit serial input. when this bit is set to 1: the source of .sa4 bit is from transmit sa4 register. 2 loop-back mode 1 auto enable r/w loop-back mode 1 auto enable : the bit enables local loop-back of the framer while a certain con - dition is happened. when this bit is 0: no local loop-back is activated. when this bit is 1: local loop-back is activated if the following condition happened from the transmit serial inputs: ? sa5 = 0 for 8 consecutive times. ? sa6 = 1111 for 8 consecutive times. ? remote yellow alarm bit (a bit) is 1. b it n umber b it n ame b it t ype b it d escription
xrt84l38 121 rev. 1.0.1 octal t1/e1/j1 framer 1 loop-back mode 2 auto enable r/w loop-back mode 2 auto enable : the bit enables local loop-back of the framer while a certain con - dition is happened. when this bit is 0: no local loop-back is activated. when this bit is 1: local loop-back is activated if the following condition happened from the transmit serial inputs: ? sa5 = 0 for 8 consecutive times. ? sa6 = 1010 for 8 consecutive times. ? remote yellow alarm bit (a bit) is 1. 0 loop-back mode release auto enable r/w loop-back mode release auto enable : the bit enables local loop-back to be released automatically if a certain condition is happened. when this bit is 0: no local loop-back is released. when this bit is 1: local loop-back is released if the following condition happened from the transmit serial inputs: ? sa5 = 0 for 8 consecutive times. ? sa6 = 0000 for 8 consecutive times. transmit sa4 register (tsa4r) (indirect address = 0xn0h, 0x33h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa4 bit[7:0] r/w 1 1 1 1 1 1 1 1 b it n umber b it n ame b it t ype b it d escription 7-0 transmit sa4 bit[7:0] r/w transmit sa4 bit[7:0]: these read/write bit fields determine contents of the sa4 bits when transmit sa4 enable bit is 0 and transmit sa4 select bit is 1. bit 7 of this register is transmitted as sa4 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa4 bit in frame 4 of the crc-4 multi-frame, etc. b it n umber b it n ame b it t ype b it d escription
xrt84l38 122 octal t1/e1/j1 framer rev. 1.0.1 transmit sa5 register (tsa5r) (indirect address = 0xn0h, 0x34h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa5 bit[7:0] r/w 1 1 1 1 1 1 1 1 b it n umber b it n ame b it t ype b it d escription 7-0 transmit sa5 bit[7:0] r/w transmit sa5 bit[7:0]: these read/write bit fields determine contents of the sa5 bits when transmit sa5 enable bit is 0 and transmit sa5 select bit is 1. bit 7 of this register is transmitted as sa5 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa5 bit in frame 4 of the crc-4 multi-frame, etc. transmit sa6 register (tsa6r) (indirect address = 0xn0h, 0x35h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa6 bit[7:0] r/w 1 1 1 1 1 1 1 1 b it n umber b it n ame b it t ype b it d escription 7-0 transmit sa6 bit[7:0] r/w transmit sa6 bit[7:0]: these read/write bit fields determine contents of the sa6 bits when transmit sa6 enable bit is 0 and transmit sa6 select bit is 1. bit 7 of this register is transmitted as sa6 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa6 bit in frame 4 of the crc-4 multi-frame, etc. transmit sa7 register (tsa7r) (indirect address = 0xn0h, 0x36h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa7 bit[7:0] r/w 1 1 1 1 1 1 1 1
xrt84l38 123 rev. 1.0.1 octal t1/e1/j1 framer b it n umber b it n ame b it t ype b it d escription 7-0 transmit sa7 bit[7:0] r/w transmit sa7 bit[7:0]: these read/write bit fields determine contents of the sa7 bits when transmit sa7 enable bit is 0 and transmit sa7 select bit is 1. bit 7 of this register is transmitted as sa7 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa7 bit in frame 4 of the crc-4 multi-frame, etc. transmit sa8 register (tsa8r) (indirect address = 0xn0h, 0x37h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit sa8 bit[7:0] r/w 1 1 1 1 1 1 1 1 b it n umber b it n ame b it t ype b it d escription 7-0 transmit sa8 bit[7:0] r/w transmit sa8 bit[7:0]: these read/write bit fields determine contents of the sa8 bits when transmit sa8 enable bit is 0 and transmit sa8 select bit is 1. bit 7 of this register is transmitted as sa8 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa8 bit in frame 4 of the crc-4 multi-frame, etc. receive sa4 register (rsa4r) (indirect address = 0xn0h, 0x3bh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa4 bit[7:0] r 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 receive sa4 bit[7:0] r/w receive sa4 bit[7:0]: these read/write bit fields store contents of the sa4 bits received from the incoming serial data. bit 7 of this register is received as sa4 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa4 bit in frame 4 of the crc-4 multi-frame, etc.
xrt84l38 124 octal t1/e1/j1 framer rev. 1.0.1 receive sa5 register (rsa5r) (indirect address = 0xn0h, 0x3ch) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa5 bit[7:0] r 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 receive sa5 bit[7:0] r/w receive sa5 bit[7:0]: these read/write bit fields store contents of the sa5 bits received from the incoming serial data. bit 7 of this register is received as sa5 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa5 bit in frame 4 of the crc-4 multi-frame, etc. receive sa6 register (rsa6r) (indirect address = 0xn0h, 0x3dh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa6 bit[7:0] r 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 receive sa6 bit[7:0] r/w receive sa6 bit[7:0]: these read/write bit fields store contents of the sa6 bits received from the incoming serial data. bit 7 of this register is received as sa6 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa6 bit in frame 4 of the crc-4 multi-frame, etc. receive sa7 register (rsa7r) (indirect address = 0xn0h, 0x3eh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa7 bit[7:0] r 0 0 0 0 0 0 0 0
xrt84l38 125 rev. 1.0.1 octal t1/e1/j1 framer b it n umber b it n ame b it t ype b it d escription 7-0 receive sa7 bit[7:0] r/w receive sa7 bit[7:0]: these read/write bit fields store contents of the sa7 bits received from the incoming serial data. bit 7 of this register is received as sa7 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa7 bit in frame 4 of the crc-4 multi-frame, etc. receive sa8 register (rsa8r) (indirect address = 0xn0h, 0x3fh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive sa8 bit[7:0] r 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 receive sa8 bit[7:0] r/w receive sa8 bit[7:0]: these read/write bit fields store contents of the sa8 bits received from the incoming serial data. bit 7 of this register is received as sa8 bit in frame 2 of the crc-4 multi-frame. bit 6 of this register is transmitted as sa8 bit in frame 4 of the crc-4 multi-frame, etc. transmit channel control register (rccr) (indirect address = 0xn02h, 0x00h - 0x1fh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lapd select bit 1 lapd select bit 0 transmit zero code suppression select bit [1:0] (t1 mode only) transmit conditioning select bit [3:0] r/w r/w r/w r/w r/w r/w 1 0 0 0 0 0 0 0
xrt84l38 126 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7-6 lapd select bit [1:0] r/w lapd select bit [1:0]: when these bits are set to 00: the first lapd channel is used as data source for d or e time slot. when these bits are set to 01: the second lapd channel is used as data source for d or e time slot. when these bits are set to 10: in t1 mode, the transmit d/e timeslot source select bits (txde[1:0]) of the transmit data link select register (tsdlsr) will determine the data source for d/e time slot. in e1 mode, the transmit signaling and data link source select bits (txsigdl[2:0]) of the transmit data link select register (tsdlsr) will determine the data source for d/e time slot. when these bits are set to 11: the third lapd channel is used as data source for d or e time slot. 5-4 transmit zero code suppression select {t1 mode only} r/w transmit zero code suppression select: when these bits are set to 00: the input ds1 pcm data of this ds0 channel is unchanged. no zero code suppression is used. when these bits are set to 01: at&t bit 7 stuffing is used and the input ds1 pcm data of this ds0 channel is modified. when these bits are set to 10: gte zero code suppression is and the input ds1 pcm data of this ds0 channel is modified. when these bits are set to 11: dds zero code suppression is and the input ds1 pcm data of this ds0 channel is modified.
xrt84l38 127 rev. 1.0.1 octal t1/e1/j1 framer 3-0 transmit conditioning select r/w transmit conditioning select: when these bits are set to 0000: the input ds1 pcm data of this ds0 channel is unchanged. when these bits are set to 0001: all 8 bits of the input ds1 pcm data of this ds0 channel are inverted. when these bits are set to 0010: the even bits of the input ds1 pcm data of this ds0 channel are inverted. when these bits are set to 0011: the odd bits of the input ds1 pcm data of this ds0 channel are inverted. when these bits are set to 0100: the input ds1 pcm data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). when these bits are set to 0101: the input ds1 pcm data of this ds0 channel are replaced by busy code (0x7f). when these bits are set to 0110: the input ds1 pcm data of this ds0 channel are replaced by vacant code (0xff). when these bits are set to 0111: the input ds1 pcm data of this ds0 channel are replaced by busy_ts code (111xxxxx). when these bits are set to 1000: the input ds1 pcm data of this ds0 channel are replaced by mux-out-of-frame (moof) code with value 0x1a. when these bits are set to 1001: the input ds1 pcm data of this ds0 channel are replaced by the a-law digital milliwatt pattern. when these bits are set to 1010: the input ds1 pcm data of this ds0 channel are replaced by the u-law digital milliwatt pattern. when these bits are set to 1011: the msb bit of the input ds1 pcm data of this ds0 channel is inverted. when these bits are set to 1100: all bits of the input ds1 pcm data of this ds0 channel except msb bit are inverted. when these bits are set to 1101: the input ds1 pcm data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. when these bits are set to 1110: the input ds1 pcm data of this ds0 channel is unchanged. when these bits are set to 1111: this channel is configured as d or e timeslot. b it n umber b it n ame b it t ype b it d escription
xrt84l38 128 octal t1/e1/j1 framer rev. 1.0.1 user idle code register (ucr) (indirect address = 0xn02h, 0x20h - 0x3fh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user idle code bit [7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 user idle code r/w user idle code: these read/write bit-fields permits the user store any value of idle code into the framer. when the transmit data condition - ing select [3:0] bits of tccr register of a particular ds0 channel are set to 0100, the input e1 pcm data are replaced by contents of this register and sent to the transmit liu interface. transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 signaling bit a signaling bit b signaling bit c signaling bit d reserved robbed-bit signaling enable transmit robbed-bit signaling source control bit 1 transmit robbed-bit signaling source control bit 0 r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 signaling bit a r/w signaling bit a: this bit is used to store signaling bit a that is sent as the least significant bit of timeslot of frame number 6. 6 signaling bit b r/w signaling bit b: this bit is used to store signaling bit b that is sent as the least significant bit of timeslot of frame number 12. 5 signaling bit c r/w signaling bit c: this bit is used to store signaling bit c that is sent as the least significant bit of timeslot of frame number 18. 4 signaling bit d r/w signaling bit d: this bit is used to store signaling bit d that is sent as the least significant bit of timeslot of frame number 24.
xrt84l38 129 rev. 1.0.1 octal t1/e1/j1 framer 2 robbed-bit signaling enable r/w robbed-bit signaling enable: when these bits are set to 0: robbed-bit signaling is disabled. no signaling data will be inserted into the input pcm data no matter what the setting of the transmit signaling source select [1:0] bits is. when these bits are set to 1: signaling data is enabled and inserted into the input ds1 pcm data according to setting of the transmit signaling source select [1:0] bits. 1-0 transmit signaling source select r/w transmit signaling source select: when these bits are set to 00: none of the signaling data, the cas multi-frame alignment pat - tern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data by the framer. however, the user can embed the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y into e1 pcm data before routing the pcm data into the framer. when these bits are set to 01: the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from tscr register of each timeslot. when these bits are set to 10: if the xrt84l38 framer is operating in e1 2.048mbit/s mode and if the txfr2048 bit of the transmit interface control register (ticr) is set to zero: the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from the txoh_n input pin. if the xrt84l38 framer is operating in e1 2.048mbit/s mode and if the txfr2048 bit of the transmit interface control register (ticr) is set to one: the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from the txsig_n input pin. when these bits are set to 11: no signaling data or the cas multi-frame alignment pattern is inserted into the input e1 pcm data by the framer. however, the user can embed signaling data into e1 pcm data before routing the pcm data into the framer. the x bit is inserted into the outgoing e1 pcm data from tscr register. the cas multi-frame yellow alarm y bit is generated by the xrt84l38 framer depends on operating condition of the e1 link. b it n umber b it n ame b it t ype b it d escription
xrt84l38 130 octal t1/e1/j1 framer rev. 1.0.1 receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive lapd channel select bit 1 receive lapd channel select bit 0 receive zero code suppression select bit [1:0] (t1 mode only) receive conditioning select bit [3:0] r/w r/w r/w r/w r/w r/w 1 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-6 receive lapd channel select [1:0] receive lapd channel select bit [1:0]: when these bits are set to 00: the first lapd channel is used as data destination for d or e time slot. when these bits are set to 01: the second lapd channel is used as data destination for d or e time slot. when these bits are set to 10: in t1 mode, the transmit d/e timeslot source select bits (txde[1:0]) of the transmit data link select register (tsdlsr) will determine the data destination for d/e time slot. in e1 mode, the transmit signaling and data link source select bits (txsigdl[2:0]) of the transmit data link select register (tsdlsr) will determine the data destination for d/e time slot. when these bits are set to 11: the third lapd channel is used as data destination for d or e time slot. 6 reserved 5-4 receive zero code suppression select {t1 mode only} r/w receive zero code suppression select: when these bits are set to 00: the received ds1 payload data of this ds0 channel is unchanged. no zero code suppression is used. when these bits are set to 01: at&t bit 7 stuffing is used. when these bits are set to 10: gte zero code suppression is used. when these bits are set to 11: dds zero code suppression is used.
xrt84l38 131 rev. 1.0.1 octal t1/e1/j1 framer 3-0 receive conditioning select r/w receive conditioning select: when these bits are set to 0000: the received ds1 payload data of this ds0 channel is unchanged. when these bits are set to 0001: all 8 bits of the input ds1 payload data of this ds0 channel are inverted. when these bits are set to 0010: the even bits of the input ds1 payload data of this ds0 channel are inverted. when these bits are set to 0011: the odd bits of the input ds1 payload data of this ds0 channel are inverted. when these bits are set to 0100: the input ds1 payload data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). when these bits are set to 0101: the input ds1 payload data of this ds0 channel are replaced by busy code (0x7f). when these bits are set to 0110: the input ds1 payload data of this ds0 channel are replaced by vacant code (0xff). when these bits are set to 0111: the input ds1 payload data of this ds0 channel are replaced by busy_ts code (111xxxxx). when these bits are set to 1000: the input ds1 payload data of this ds0 channel are replaced by mux-out-of-frame (moof) code with value 0x1a. when these bits are set to 1001: the input ds1 payload data of this ds0 channel are replaced by the a-law digital milliwatt pattern. when these bits are set to 1010: the input ds1 payload data of this ds0 channel are replaced by the u-law digital milliwatt pattern. when these bits are set to 1011: the msb bit of the input ds1 payload data of this ds0 channel is inverted. when these bits are set to 1100: all bits of the input ds1 payload data of this ds0 channel except msb bit are inverted. when these bits are set to 1101: the input ds1 payload data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. when these bits are set to 1110: the input ds1 payload data of this ds0 channel is unchanged. when these bits are set to 1111: this channel is configured as d or e timeslot. b it n umber b it n ame b it t ype b it d escription
xrt84l38 132 octal t1/e1/j1 framer rev. 1.0.1 receive user idle code register (ucr) (indirect address = 0xn02h, 0x80h - 0x97h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive user idle code bit [7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-0 receive user idle code r/w receive user idle code: these read/write bit-fields permits the user store any value of idle code into the framer. when the receive data condition - ing select [3:0] bits of rccr regi ster of a particular ds0 channel are set to 0100, the received ds1 payload data are replaced by contents of this register and sent to the terminal equipment. receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xb7h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved receive signaling substitution enable receive signaling output enable de-bounce enable receive signaling substitution control bit 1 receive signaling substitution control bit 0 signaling extraction control bit 1 signaling extraction control bit 0 r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 reserved 6 receive signaling substitution enable r/w receive signaling substitution enable: when this bit is set to 0: signaling substitution is disabled. the xrt84l38 framer will not replace extracted signaling bits from the incoming ds1 payload data with all ones or with signaling bits stored in rssr registers. when this bit is set to 1: signaling substitution is enabled. the xrt84l38 framer will replace extracted signaling bits from the incoming ds1 payload data with all ones or with signaling bits stored in rssr registers.
xrt84l38 133 rev. 1.0.1 octal t1/e1/j1 framer 5 receive signaling output enable r/w receive signaling output enable: when these bits are set to 0: the xrt84l38 framer will not send extracted signaling bits from the incoming ds1 payload data to external equipment through the receive signaling output pin (rxsig_n). when these bits are set to 1: the xrt84l38 framer will send extracted signaling bits from the incoming ds1 payload data to external equipment through the receive signaling output pin (rxsig_n). 4 3-2 receive signaling substitution control r/w receive signaling substitution control: when these bits are set to 00: the received signaling bits are replaced by all ones and send to the external equipment. when these bits are set to 01: two-code signaling substitution is applied to the received signal - ing bits. the replaced signaling information is sent to the exter - nal equipment. when these bits are set to 10: four-code signaling substitution is applied to the received signal - ing bits. the replaced signaling information is sent to the exter - nal equipment. when these bits are set to 11: sixteen-code signaling substitution is applied to the received sig - naling bits. the replaced signaling information is sent to the external equipment. n ote : in sf mode, this option is disabled. 1-0 signaling extraction control r/w signaling extraction control: when these bits are set to 00: the xrt84l38 framer does not extract signaling information from incoming ds1 payload data. when these bits are set to 01: the xrt84l38 framer extracts sixteen-code signaling informa - tion from incoming ds1 payload data. when these bits are set to 10: the xrt84l38 framer extracts four-code signaling information from incoming ds1 payload data. when these bits are set to 11: the xrt84l38 framer extracts two-code signaling information from incoming ds1 payload data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 134 octal t1/e1/j1 framer rev. 1.0.1 receive signaling register array (rsra )(indirect address = 0xn4h, 0x00h - 0x17h) 7-4 reserved r/w 3 sig16-a sig4-a sig2-a sixteen-code signaling bit a four-code signaling bit a two-code signaling bit a 2 sig16-b sig4-b sig2-a sixteen-code signaling bit b four-code signaling bit b two-code signaling bit a 1 sig16-c sig4-a sig2-a sixteen-code signaling bit c four-code signaling bit a two-code signaling bit a 0 sig16-d sig4-b sig2-a sixteen-code signaling bit d four-code signaling bit b two-code signaling bit a 3 signaling bit a r/w signaling bit a: this bit is used to store signaling bit a that is received and extracted as the least significant bit of timeslot of frame number 6. 2 signaling bit b r/w signaling bit b: this bit is used to store signaling bit b that is received and extracted as the least significant bit of timeslot of frame number 12. 1 signaling bit c r/w signaling bit c: this bit is used to store signaling bit c that is received and extracted as the least significant bit of timeslot of frame number 18. 0 signaling bit d r/w signaling bit d: this bit is used to store signaling bit d that is received and extracted as the least significant bit of timeslot of frame number 24. b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 prbs type select error insertion data inversion select receive prbs lock indication receive prbs block enable transmit prbs block enable receive ds1/e1 framer bypassed transmit ds1/e1 framer bypassed r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt84l38 135 rev. 1.0.1 octal t1/e1/j1 framer block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sa6 inter - rupt loop-back code interrupt receive clock loss interrupt one second interrupt hdlc controller interrupt slip buffer interrupt alarm and error inter - rupt t1/e1 framer inter - rupt r r r r r r r r 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 sa6 interrupt r sa6 interrupt: when this bit is set to 0: no sa6 interrupt is generated. when this bit is set to 1: an sa6 interrupt is generated. 6 loop-back code interrupt r loop-back code interrupt: when this bit is set to 0: no loop-back code interrupt is generated. when this bit is set to 1: a loop-back code interrupt is generated. 5 receive clock loss inter - rupt r receive clock loss interrupt: when this bit is set to 0: no receive clock loss interrupt is generated. when this bit is set to 1: a receive clock loss interrupt is generated. 4 one second interrupt r one second interrupt: when this bit is set to 0: no one second interrupt is generated. when this bit is set to 1: a one second interrupt is generated. 3 hdlc controller interrupt r hdlc controller interrupt: when this bit is set to 0: no hdlc controller interrupt is generated. when this bit is set to 1: a hdlc controller interrupt is generated. 2 slip buffer interrupt r slip buffer interrupt: when this bit is set to 0: no t1/e1 framer interrupt is generated. when this bit is set to 1: a slip buffer interrupt is generated.
xrt84l38 136 octal t1/e1/j1 framer rev. 1.0.1 1 alarm and error interrupt r alarm and error interrupt: when this bit is set to 0: no alarm and error interrupt is generated. when this bit is set to 1: an alarm and error interrupt is generated. 0 t1/e1 framer interrupt r t1/e1 framer interrupt: when this bit is set to 0: no t1/e1 framer interrupt is generated. when this bit is set to 1: a t1/e1 framer interrupt is generated. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sa6 inter - rupt enable loop-back code interrupt enable receive clock loss interrupt enable one second interrupt enable hdlc controller interrupt enable slip buffer interrupt enable alarm and error interrupt enable t1/e1 framer inter - rupt enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 sa6 interrupt enable r sa6 interrupt enable: when this bit is set to 0: every interrupt generated by the receive sa6 interrupt register (rsair) is disabled. when this bit is set to 1: every interrupt generated by the receive sa6 interrupt register (rsair) enabled. 6 loop-back code interrupt enable r loop-back code interrupt enable: when this bit is set to 0: every interrupt generated by the receive loop-back code inter - rupt and status register (rlcisr) is disabled. when this bit is set to 1: every interrupt generated by the receive loop-back code inter - rupt and status register (rlcisr) enabled. 5 receive clock loss interrupt enable r receive clock loss interrupt enable: when this bit is set to 0: the receive clock loss interrupt is disabled. when this bit is set to 1:t he receive clock loss interrupt is enabled. b it n umber b it n ame b it t ype b it d escription
xrt84l38 137 rev. 1.0.1 octal t1/e1/j1 framer 4 one second interrupt enable r one second interrupt enable: when this bit is set to 0: one second interrupt is disabled. when this bit is set to 1: one second interrupt is enabled. 3 hdlc controller interrupt enable r hdlc controller interrupt enable: when this bit is set to 0: every interrupt generated by the data link status register (dlsr) is disabled. when this bit is set to 1: every interrupt generated by the data link status register (dlsr) is enabled. 2 slip buffer interrupt enable r slip buffer interrupt enable: when this bit is set to 0: every interrupt generated by the slip buffer status register (sbsr) is disabled. when this bit is set to 1: every interrupt generated by the slip buffer status register (sbsr) is enabled. 1 alarm and error interrupt enable r alarm and error interrupt enable: when this bit is set to 0: every interrupt generated by the alarm and error interrupt status register (aeisr) is disabled. when this bit is set to 1: every interrupt generated by the alarm and error interrupt status register (aeisr) is enabled. 0 t1/e1 framer interrupt enable r t1/e1 framer interrupt enable: when this bit is set to 0: every interrupt generated by the t1/e1 framer interrupt status register (fisr) is disabled. when this bit is set to 1: every interrupt generated by the t1/e1 framer interrupt status register (fisr) is enabled. alarm and error status register (aesr) - t1 mode (indirect address = 0xnah, 0x02h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive red alarm state receive ais state receive yellow alarm state receive loss of sig - nal change receive bipolar violation state change receive red alarm state change receive ais state change receive yellow alarm state change r r r rur / wc rur / wc rur / wc rur / wc rur / wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription
xrt84l38 138 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7 receive red alarm state r receive red alarm state: when this bit is 0: there is no red alarm condition detected in the incoming ds1 payload data. when this bit is 1: there is red alarm condition detected in the incoming ds1 pay - load data. 6 receive ais state r receive ais state: when this bit is 0: there is no ais alarm condition detected in the incoming ds1 payload data. when this bit is 1: there is ais alarm condition detected in the incoming ds1 pay - load data. 5 receive yellow alarm state r receive yellow alarm state: when this bit is 0: there is no yellow alarm condition detected in the incoming ds1 payload data. when this bit is 1: there is yellow alarm condition detected in the incoming ds1 payload data. 4 receive loss of signal change rur / wc receive loss of signal: when this bit is 0: there is no change of loss of signal state in the incoming ds1 payload data. when this bit is 1: there is change of loss of signal state in the incoming ds1 pay - load data. 3 receive bipolar violation state change rur / wc receive bipolar violation: when this bit is 0: there is no change of bipolar violation state in the incoming ds1 payload data. when this bit is 1: there is change of bipolar violation state in the incoming ds1 payload data. 2 receive red alarm state change rur / wc receive red alarm state change: when this bit is 0: there is no change of red alarm state in the incoming ds1 pay - load data. when this bit is 1: there is change of red alarm state in the incoming ds1 payload data.
xrt84l38 139 rev. 1.0.1 octal t1/e1/j1 framer 1 receive ais state change rur / wc receive ais state change: when this bit is 0: there is no change of ais state in the incoming ds1 payload data. when this bit is 1: there is change of ais state in the incoming ds1 payload data. 0 receive yellow alarm state change rur / wc receive yellow alarm state change: when this bit is 0: there is no change of yellow alarm state in the incoming ds1 payload data. when this bit is 1: there is change of yellow alarm state in the incoming ds1 pay - load data. alarm and error status register (aesr) - e1 mode (indirect address = 0xnah, 0x02h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive red alarm state receive ais state receive cas multi- frame yel - low alarm state change receive loss of sig - nal change receive bipolar violation state change receive red alarm state change receive ais state change receive yellow alarm state change r r rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 receive red alarm state r receive red alarm state: when this bit is 0: there is no red alarm condition detected in the incoming ds1 payload data. when this bit is 1: there is red alarm condition detected in the incoming ds1 pay - load data. 6 receive ais state r receive ais state: when this bit is 0: there is no ais alarm condition detected in the incoming ds1 payload data. when this bit is 1: there is ais alarm condition detected in the incoming ds1 pay - load data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 140 octal t1/e1/j1 framer rev. 1.0.1 5 receive cas multi-frame yellow alarm state change rur / wc receive cas multi-frame yellow alarm state change: when this bit is 0: there is no change of cas multi-frame yellow alarm state in the incoming e1 payload data. when this bit is 1: there is change of cas multi-frame yellow alarm state in the incoming e1 payload data. 4 receive loss of signal change rur / wc receive loss of signal: when this bit is 0: there is no change of loss of signal state in the incoming ds1 payload data. when this bit is 1: there is change of loss of signal state in the incoming ds1 pay - load data. 3 receive bipolar violation state change rur / wc receive bipolar violation: when this bit is 0: there is no change of bipolar violation state in the incoming ds1 payload data. when this bit is 1: there is change of bipolar violation state in the incoming ds1 payload data. 2 receive red alarm state change rur / wc receive red alarm state change: when this bit is 0: there is no change of red alarm state in the incoming ds1 pay - load data. when this bit is 1: there is change of red alarm state in the incoming ds1 payload data. 1 receive ais state change rur / wc receive ais state change: when this bit is 0: there is no change of ais state in the incoming ds1 payload data. when this bit is 1: there is change of ais state in the incoming ds1 payload data. 0 receive yellow alarm state change rur / wc receive yellow alarm state change: when this bit is 0: there is no change of yellow alarm state in the incoming ds1 payload data. when this bit is 1: there is change of yellow alarm state in the incoming ds1 pay - load data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 141 rev. 1.0.1 octal t1/e1/j1 framer alarm and error interrupt enable register (aeier) - t1 mode (indirect address = 0xnah, 0x03h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved receive loss of sig - nal change interrupt enable receive bipolar violation state change interrupt enable receive red alarm state change interrupt enable receive ais state change interrupt enable receive yellow alarm state change interrupt enable r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-5 reserved 4 receive loss of signal interrupt enable r/w receive loss of signal interrupt enable: when this bit is set to 0: the receive loss of signal interrupt is disabled. occurrence of loss of signals will not generate an interrupt. when this bit is set to 1: the receive loss of signal interrupt is enabled. occurrence of loss of signals will generate an interrupt. 3 receive bipolar violation interrupt enable r/w receive bipolar violation interrupt enable: when this bit is set to 0: the receive bipolar violation interrupt is disabled. occurrence of one or more bipolar violations will not generate an interrupt. when this bit is set to 1: the receive bipolar violation interrupt is enabled. occurrence of one or more bipolar violations will generate an interrupt. 2 receive red alarm state change interrupt enable r/w receive red alarm state change interrupt enable: when this bit is set to 0: the receive red alarm state change interrupt is disabled. no receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. when this bit is set to 1: the receive red alarm state change interrupt is enabled. receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. 1 receive ais state change interrupt enable r/w receive ais state change interrupt enable: when this bit is set to 0: the receive ais state change interrupt is disabled. when this bit is set to 1: the receive ais state change interrupt is enabled.
xrt84l38 142 octal t1/e1/j1 framer rev. 1.0.1 0 receive yellow alarm state change interrupt enable r/w receive yellow alarm state change interrupt enable: when this bit is set to 0: the receive yellow alarm state change interrupt is disabled. any state change of receive yellow alarm will not generate an interrupt. when this bit is set to 1: the receive yellow alarm state change interrupt is enabled. any state change of receive yellow alarm will generate an inter - rupt. alarm and error interrupt enable register (aeier) - e1 mode (indirect address = 0xnah, 0x03h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved receive cas multi- frame yel - low alarm state change interrupt enable receive loss of sig - nal change interrupt enable receive bipolar violation state change interrupt enable receive red alarm state change interrupt enable receive ais state change interrupt enable receive yellow alarm state change interrupt enable r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7-6 reserved 5 receive cas multi-frame yellow alarm state change interrupt enable r/w receive cas multi-frame yellow alarm state change inter - rupt enable: when this bit is set to 0: the receive cas multi-frame yellow alarm state change inter - rupt is disabled. any state change of receive cas multi-frame yellow alarm will not generate an interrupt. when this bit is set to 1: the receive cas multi-frame yellow alarm state change inter - rupt is enabled. any state change of receive cas multi-frame yellow alarm will generate an interrupt. 4 receive loss of signal interrupt enable r/w receive loss of signal interrupt enable: when this bit is set to 0: the receive loss of signal interrupt is disabled. occurrence of loss of signals will not generate an interrupt. when this bit is set to 1: the receive loss of signal interrupt is enabled. occurrence of loss of signals will generate an interrupt. b it n umber b it n ame b it t ype b it d escription
xrt84l38 143 rev. 1.0.1 octal t1/e1/j1 framer 3 receive bipolar violation interrupt enable r/w receive bipolar violation interrupt enable: when this bit is set to 0: the receive bipolar violation interrupt is disabled. occurrence of one or more bipolar violations will not generate an interrupt. when this bit is set to 1: the receive bipolar violation interrupt is enabled. occurrence of one or more bipolar violations will generate an interrupt. 2 receive red alarm state change interrupt enable r/w receive red alarm state change interrupt enable: when this bit is set to 0: the receive red alarm state change interrupt is disabled. no receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. when this bit is set to 1: the receive red alarm state change interrupt is enabled. receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. 1 receive ais state change interrupt enable r/w receive ais state change interrupt enable: when this bit is set to 0: the receive ais state change interrupt is disabled. when this bit is set to 1: the receive ais state change interrupt is enabled. 0 receive yellow alarm state change interrupt enable r/w receive yellow alarm state change interrupt enable: when this bit is set to 0: the receive yellow alarm state change interrupt is disabled. any state change of receive yellow alarm will not generate an interrupt. when this bit is set to 1: the receive yellow alarm state change interrupt is enabled. any state change of receive yellow alarm will generate an inter - rupt. framer interrupt status register (fisr) (indirect address = 0xnah, 0x04h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 cas multi-frame alignment changed (e1 only) national bit updated (e1 only) signaling updated frame alignment changed f r am er in-frame state frame mimic state changed synchroniza - tion bit error framing error rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription
xrt84l38 144 octal t1/e1/j1 framer rev. 1.0.1 b it n umber b it n ame b it t ype b it d escription 7 cas multi-frame alignment changed (e1 only) rur / wc cas multi-frame alignment changed: when this bit is 0: there is no change of cas multi-frame alignment in the incom - ing e1 payload data. when this bit is 1: there is change of cas multi-frame alignment in the incoming e1 payload data. 6 national bit updated (e1 only) rur / wc national bit updated: when this bit is 0: there is no change of national bits in the incoming e1 payload data. when this bit is 1: there is change of national bits in the incoming e1 payload data. 5 signaling updated rur / wc signaling updated: when this bit is 0: there is no change of signaling information in the incoming ds1/ e1 payload data. when this bit is 1: there is change of signaling information in the incoming ds1/e1 payload data. 4 frame alignment changed rur / wc frame alignment changed: when this bit is 0: there is no change of frame alignment in the incoming ds1/e1 payload data. when this bit is 1: there is change of frame alignment in the incoming ds1/e1 payload data. 3 framer in-frame state rur / wc framer in-frame state: when this bit is 0: there is no change occur in the in-frame state in the incoming ds1/e1 payload data. that is, if the framer is in-frame before, then it is remained in-frame. when this bit is 1: there is change of in-frame state in the incoming ds1/e1 pay - load data. that is, if the framer is in-frame before, then it is out- of-frame now. 2 frame mimic state changed rur / wc frame mimic state changed: when this bit is 0: there is no change frame mimic state in the incoming ds1/e1 payload data. when this bit is 1: there is change of frame mimic state in the incoming ds1/e1 payload data.
xrt84l38 145 rev. 1.0.1 octal t1/e1/j1 framer 1 synchronization bit error rur / wc synchronization bit error: when this bit is 0: there is no synchronization bit error in the incoming ds1/e1 payload data. when this bit is 1: there is synchronization bit error in the incoming ds1/e1 pay - load data. 0 framing error rur / wc framing error: when this bit is 0: there is no framing error in the incoming ds1/e1 payload data. when this bit is 1: there is framing error in the incoming ds1/e1 payload data. framer interrupt enable register (fier) (indirect address = 0xnah, 0x05h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 cas multi-frame alignment change interrupt enabl e (e1 only) national bit update interrupt enable (e1 only) signaling update interrupt enable frame alignment change interrupt enable f r am er in-frame state interrupt enable frame mimic state change interrupt enable synchroniza - tion bit error interrupt enable framing error inter - rupt enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 cas multi-frame alignment change interrupt enable (e1 only) rur / wc cas multi-frame alignment changed interrupt enable: when this bit is set to 0: the cas multi-frame alignment change interrupt is disabled. when this bit is set to 1: the cas multi-frame alignment changed interrupt is enabled. 6 national bit update interrupt enable (e1 only) rur / wc national bit updated interrupt enable: when this bit is set to 0: the national bit update interrupt is disabled. when this bit is set to 1: the national bit update interrupt is enabled. 5 signaling update interrupt enable rur / wc signaling updated interrupt enable: when this bit is set to 0: the signaling update interrupt is disabled. when this bit is set to 1: the signaling update interrupt is enabled. b it n umber b it n ame b it t ype b it d escription
xrt84l38 146 octal t1/e1/j1 framer rev. 1.0.1 4 frame alignment change interrupt enable rur / wc frame alignment changed interrupt enable: when this bit is set to 0: the frame alignment change interrupt is disabled. when this bit is set to 1: the frame alignment change interrupt is enabled. 3 framer in-frame state interrupt enable rur / wc framer in-frame state interrupt enable:when this bit is set to 0:the framer in-frame state interrupt is disabled. when this bit is set to 1:the framer in-frame state interrupt is enabled. 2 frame mimic state change interrupt enable rur / wc frame mimic state changed interrupt enable: when this bit is set to 0: he frame mimic state change interrupt is disabled. when this bit is set to 1: the frame mimic state change interrupt is enabled. 1 synchronization bit error interrupt enable rur / wc synchronization bit error interrupt enable: when this bit is set to 0: the synchronization bit error interrupt is disabled. when this bit is set to 1: the synchronization bit error interrupt is enabled. 0 framing error interrupt enable rur / wc framing error interrupt enable: when this bit is set to 0: the framing error interrupt is disabled. when this bit is set to 1: the framing error interrupt is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 message type transmit start of transfer receive start of transfer transmit end of transfer receive end of transfer frame check sequence error detection receive abort sequence receive idle flag sequence rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc rur / wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 message type rur / wc message type: when this bit is set to 0: the receive hdlc controller receives and processes bit-ori - ented signaling (bos) message. when this bit is set to 1: the receive hdlc controller receives and processes lapd protocol or message-oriented signaling (mos) message. b it n umber b it n ame b it t ype b it d escription
xrt84l38 147 rev. 1.0.1 octal t1/e1/j1 framer 6 transmit start of transfer rur / wc transmit start of transfer: when this bit is 0: there is no data link message to be sent to the data link channel. when this bit is 1: the hdlc controller will send a data link message to the data link channel. 5 receive start of transfer rur / wc receive start of transfer: when this bit is 0: there is no data link message in the data link channel. when this bit is 1: the hdlc controller began to receive a data link message in the data link channel. 4 transmit end of transfer rur / wc transmit end of transfer: when this bit is 0: no data link message was sent to the data link channel. when this bit is 1: the hdlc controller finished sending a data link message to the data link channel. 3 receive end of transfer rur / wc receive end of transfer: when this bit is 0: no data link message was present in the data link channel. when this bit is 1: the hdlc controller finished receiving a data link message in the data link channel. 2 frame check sequence error detection rur / wc frame check sequence error detection: when this bit is 0: there is no fcs error detected in the data link channel. when this bit is 1: the hdlc controller receives an erroneous fcs in the data link channel. 1 receive abort sequence rur / wc receive abort sequence: when this bit is 0: there is no bos abort sequence received in the data link channel. when this bit is 1: the hdlc controller receives mos abort sequence in the data link channel. 0 receive idle flag sequence rur / wc receive idle flag sequence: when this bit is 0: the message received in the data link channel is bos message. when this bit is 1: the message received in the data link channel is mos mes - sage. b it n umber b it n ame b it t ype b it d escription
xrt84l38 148 octal t1/e1/j1 framer rev. 1.0.1 data link interrupt enable register (dlier) (indirect address = 0xnah, 0x07h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserve transmit start of transfer interrupt enable receive start of transfer interrupt enable transmit end of transfer interrupt enable receive end of transfer interrupt enable frame check sequence error detection interrupt enable receive abort sequence interrupt enable receive idle flag sequence interrupt enable r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 reserved 6 transmit start of transfer interrupt enable r/w transmit start of transfer interrupt enable: when this bit is set to 0: the transmit start of transfer interrupt is disabled. when this bit is set to 1: the transmit start of transfer interrupt is enabled. 5 receive start of transfer interrupt enable r/w receive start of transfer interrupt enable: when this bit is set to 0: the receive start of transfer interrupt is disabled. when this bit is set to 1: the receive start of transfer interrupt is enabled. 4 transmit end of transfer interrupt enable r/w transmit end of transfer interrupt enable: when this bit is set to 0: the transmit end of transfer interrupt is disabled. when this bit is set to 1: the transmit end of transfer interrupt is enabled. 3 receive end of transfer interrupt enable r/w receive end of transfer interrupt enable: when this bit is set to 0: the receive end of transfer interrupt is disabled. when this bit is set to 1: the receive end of transfer interrupt is enabled. 2 frame check sequence error detection interrupt enable r/w frame check sequence error detection interrupt enable: when this bit is set to 0: the frame check sequence error detection interrupt is dis - abled. when this bit is set to 1: the frame check sequence error detection interrupt is enabled.
xrt84l38 149 rev. 1.0.1 octal t1/e1/j1 framer 1 receive abort sequence interrupt enable r/w receive abort sequence interrupt enable: when this bit is set to 0: the receive abort sequence interrupt is disabled. when this bit is set to 1: the receive abort sequence interrupt is enabled. 0 receive idle flag sequence interrupt enable r/w receive idle flag sequence interrupt enable: when this bit is set to 0: the receive idle flag sequence interrupt is disabled. when this bit is set to 1: the receive idle flag sequence interrupt is enabled. slip buffer status register (sbsr) (indirect address = 0xnah, 0x08h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit slip buffer full transmit slip buffer empty transmit slip buffer slip slc96 in synchroniza - tion multi-frame in synchro - nization receive slip buffer full receive slip buffer empty receive slip buffer slip rur/wc rur/wc rur/wc r r rur/wc rur/wc rur/wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 transmit slip buffer full rur/ wc transmit slip buffer full: when this bit is set to 0: the transmit slip buffer is not full. when this bit is set to 1: the transmit slip buffer is full and one frame of data is dis - carded. 6 transmit slip buffer empty rur/ wc transmit slip buffer empty: when this bit is set to 0: the transmit slip buffer is not empty. when this bit is set to 1: the transmit slip buffer is empty and one frame of data is repeated. 5 transmit slip buffer slip rur/ wc transmit slip buffer slip: when this bit is set to 0: the transmit slip buffer does not slip. when this bit is set to 1: the transmit slip buffer slips since either full or emptied. b it n umber b it n ame b it t ype b it d escription
xrt84l38 150 octal t1/e1/j1 framer rev. 1.0.1 4 slc96 in synchroniza - tion r slc96 in synchronization: when this bit is set to 0: the framer is not in slc96 synchronization. when this bit is set to 1: the framer is in slc96 synchronization. 3 multi-frame in synchroni - zation r multi-frame in synchronization: when this bit is set to 0: the framer is not in multi-frame synchronization. when this bit is set to 1: the framer is in multi-frame synchronization. 2 receive slip buffer full rur/ wc receive slip buffer full: when this bit is set to 0: the receive slip buffer is not full. when this bit is set to 1: the receive slip buffer is full and one frame of data is dis - carded. 1 receive slip buffer empty rur/ wc receive slip buffer empty: when this bit is set to 0: the receive slip buffer is not empty. when this bit is set to 1: the receive slip buffer is empty and one frame of data is repeated. 0 receive slip buffer slip rur/ wc receive slip buffer slip: when this bit is set to 0: the receive slip buffer does not slip. when this bit is set to 1: the receive slip buffer slips since either full or emptied. slip buffer interrupt enable register (sbier) (indirect address = 0xnah, 0x09h) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit slip buffer full interrupt enable transmit slip buffer empty interrupt enable transmit slip buffer slip interrupt enable reserved reserved receive slip buffer full interrupt enable receive slip buffer empty interrupt enable receive slip buffer slip interrupt enable r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription
xrt84l38 151 rev. 1.0.1 octal t1/e1/j1 framer b it n umber b it n ame b it t ype b it d escription 7 transmit slip buffer full interrupt enable r/w transmit slip buffer full interrupt enable: when this bit is set to 0: the transmit slip buffer full interrupt is disabled. when this bit is set to 1: the transmit slip buffer full interrupt is enabled. 6 transmit slip buffer empty interrupt enable r/w transmit slip buffer empty interrupt enable: when this bit is set to 0: the transmit slip buffer empty interrupt is disabled. when this bit is set to 1: the transmit slip buffer empty interrupt is enabled. 5 transmit slip buffer slip interrupt enable r/w transmit slip buffer slip interrupt enable: when this bit is set to 0: the transmit slip buffer slip interrupt is disabled. when this bit is set to 1: the transmit slip buffer slips slip interrupt is enabled. 4-3 reserved 2 receive slip buffer full interrupt enable r/w receive slip buffer full interrupt enable: when this bit is set to 0: the receive slip buffer full interrupt is disabled. when this bit is set to 1: the receive slip buffer full interrupt is enabled. 1 receive slip buffer empty interrupt enable r/w receive slip buffer empty interrupt enable: when this bit is set to 0: the receive slip buffer empty interrupt is disabled. when this bit is set to 1: the receive slip buffer empty interrupt is enabled. 0 receive slip buffer slip interrupt enable rur/ wc receive slip buffer slip interrupt enable: when this bit is set to 0: the receive slip buffer slip interrupt is disabled. when this bit is set to 1: the receive slip buffer slip interrupt is enabled.
xrt84l38 152 octal t1/e1/j1 framer rev. 1.0.1 receive loop-back code interrupt and status register (rlcisr) (indirect address = 0xnah, 0x0ah) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive auxp state receive auxp state change interrupt crc-4 to non-crc-4 inter-net - working sta - tus crc-4 to non-crc-4 inter-net - working sta - tus change interrupt receive loop-back code activation status receive loop-back code de-activa - tion status receive loop-back code activation status change interrupt receive loop-back c o de de-activa - tion status change interrupt r rur/wc r rur/wc r r rur/wc rur/wc 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 receive auxp state r receive auxp state: this bit indicates status of the receive auxp pattern. when this bit is set to 0: there is no auxp pattern detected in the receive data stream. when this bit is set to 1: there is auxp pattern detected in the receive data stream. 6 receive auxp state change interrupt rur/ wc receive auxp state change interrupt: when this bit is set to 0: there is no change in receive auxp pattern status. when this bit is set to 1: there is change in receive auxp pattern status. an interrupt will be generated upon detection of the change in receive auxp pattern. 5 crc-4 to non-crc-4 inter-networking status r crc-4 to non-crc-4 inter-networking status: this bit indicates status of the crc-4 internetworking. when this bit is set to 0: there is no crc-4 to non-crc-4 internetworking established. when this bit is set to 1: there is crc-4 to non-crc-4 internetworking established. 4 crc-4 to non-crc-4 inter-networking status change interrupt rur/ wc crc-4 to non-crc-4 inter-networking status change inter - rupt: when this bit is set to 0: there is no change in crc-4 to non-crc-4 inter-networking status. when this bit is set to 1: there is change in crc-4 to non-crc-4 inter-networking sta - tus. an interrupt will be generated upon detection of the change in crc-4 to non-crc-4 inter-networking status.
xrt84l38 153 rev. 1.0.1 octal t1/e1/j1 framer 3 receive loop-back code activation status r receive loop-back code activation status: this bit indicates status of the receive loop-back code activa - tion. when this bit is set to 0: there is no loop-back activation code detected in the receive data stream. when this bit is set to 1: there is loop-back activation code detected in the receive data stream. 2 receive loop-back code de-activation status r receive loop-back code de-activation status: this bit indicates status of the receive loop-back code de-acti - vation. when this bit is set to 0: there is no loop-back de-activation code detected in the receive data stream. when this bit is set to 1: there is loop-back de-activation code detected in the receive data stream. 1 receive loop-back code activation status change interrupt rur/ wc receive loop-back code activation status change inter - rupt: when this bit is set to 0: there is no change in receive loop-back activation code sta - tus. when this bit is set to 1: there is change in receive loop-back activation code status. an interrupt will be generated upon detection of the change in receive loop-back activation code status. 0 receive loop-back code de-activation status change interrupt rur/ wc receive loop-back code de-activation status change inter - rupt: when this bit is set to 0: there is no change in receive loop-back de-activation code status. when this bit is set to 1: there is change in receive loop-back de-activation code sta - tus. an interrupt will be generated upon detection of the change in receive loop-back de-activation code status. b it n umber b it n ame b it t ype b it d escription
xrt84l38 154 octal t1/e1/j1 framer rev. 1.0.1 receive loop-back code enable register (rlcer) (indirect address = 0xnah, 0x0bh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved receive auxp state change interrupt enable reserved crc-4 to non-crc-4 inter-net - working sta - tus change interrupt enable reserved reserved receive loop-back code activation status change interrupt enable receive loop-back code de- activation status change interrupt enable r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 reserved 6 receive auxp state change interrupt enable r/w receive auxp state change interrupt enable: when this bit is set to 0: the receive auxp state change interrupt is disabled. when this bit is set to 1: the receive auxp state change interrupt is enabled. 5 reserved 4 crc-4 to non-crc-4 inter-networking status change interrupt enable r/w crc-4 to non-crc-4 inter-networking status change inter - rupt enable: when this bit is set to 0: the crc-4 to non-crc-4 inter-networking status change inter - rupt is disabled. when this bit is set to 1: the crc-4 to non-crc-4 inter-networking status change inter - rupt is enabled. 3 reserved 2 receive loop-back code activation status change interrupt enable r/w receive loop-back code activation status change interrupt enable: when this bit is set to 0: the receive loop-back code activation status change inter - rupt is disabled. when this bit is set to 1: the receive loop-back code activation status change inter - rupt is enabled. 1 reserved
xrt84l38 155 rev. 1.0.1 octal t1/e1/j1 framer 0 receive loop-back code de-activation status change interrupt enable r/w receive loop-back code de-activation status change inter - rupt enable: when this bit is set to 0: the receive loop-back code de-activation status change interrupt is disabled. when this bit is set to 1: the receive loop-back code de-activation status change interrupt is enabled. receive sa interrupt register (rsair) (indirect address = 0xnah, 0x0ch) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received sa6 = 1111 interrupt received sa6 = 1110 interrupt received sa6 = 1100 interrupt received sa6 = 1010 interrupt received sa6 = 1000 interrupt received sa6 = 001x interrupt received sa6 = oth - ers interrupt received sa6 = 0000 interrupt r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 received sa6 = 1111 r/w received sa6 = 1111: when this bit is 0: a de-bounced sa6 bit of value equal to '1111' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '1111' has been received from the incoming serial data. 6 received sa6 = 1110 r/w received sa6 = 1110: when this bit is 0: a de-bounced sa6 bit of value equal to '1110' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '1110' has been received from the incoming serial data. 5 received sa6 = 1100 r/w received sa6 = 1100: when this bit is 0: a de-bounced sa6 bit of value equal to '1100' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '1100' has been received from the incoming serial data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 156 octal t1/e1/j1 framer rev. 1.0.1 4 received sa6 = 1010 r/w received sa6 = 1010: when this bit is 0: a de-bounced sa6 bit of value equal to '1010' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '1010' has been received from the incoming serial data. 3 received sa6 = 1000 r/w received sa6 = 1000: when this bit is 0: a de-bounced sa6 bit of value equal to '1000' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '1000' has been received from the incoming serial data. 2 received sa6 = 001x r/w received sa6 = 001x: when this bit is 0: a de-bounced sa6 bit of value equal to '001x' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '001x' has been received from the incoming serial data.note:x can be either 0 or 1. 1 received sa6 = others r/w received sa6 = others: when this bit is 0: a de-bounced sa6 bit of value equal to anything but other than '1111', '1110', '1100', '1000', '001x' and '0000' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to anything but other than '1111', '1110', '1100', '1000', '001x' and '0000' has been received from the incoming serial data. 0 received sa6 = 0000 r/w received sa6 = 0000: when this bit is 0: a de-bounced sa6 bit of value equal to '0000' has not been received from the incoming serial data. when this bit is 1: a de-bounced sa6 bit of value equal to '0000' has been received from the incoming serial data. b it n umber b it n ame b it t ype b it d escription
xrt84l38 157 rev. 1.0.1 octal t1/e1/j1 framer receive sa interrupt enable register (rsaier) (indirect address = 0xnah, 0x0dh) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received sa6 = 1111 interrupt enable received sa6 = 1110 interrupt enable received sa6 = 1100 interrupt enable received sa6 = 1010 interrupt enable received sa6 = 1000 interrupt enable received sa6 = 001x interrupt enable received sa6 = oth - ers interrupt enable received sa6 = 0000 interrupt enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 b it n umber b it n ame b it t ype b it d escription 7 received sa6 = 1111 interrupt enable r/w received sa6 = 1111 interrupt enable: when this bit is 0: the received sa6 = 1111 interrupt is disabled. when this bit is 1: the received sa6 = 1111 interrupt is enabled. 6 received sa6 = 1110 interrupt enable r/w received sa6 = 1110 interrupt enable: when this bit is 0: the received sa6 = 1110 interrupt is disabled. when this bit is 1: the received sa6 = 1110 interrupt is enabled. 5 received sa6 = 1100 interrupt enable r/w received sa6 = 1100 interrupt enable: when this bit is 0: the received sa6 = 1100 interrupt is disabled. when this bit is 1: the received sa6 = 1100 interrupt is enabled. 4 received sa6 = 1010 interrupt enable r/w received sa6 = 1010 interrupt enable: when this bit is 0: the received sa6 = 1010 interrupt is disabled. when this bit is 1: the received sa6 = 1010 interrupt is enabled. 3 received sa6 = 1000 interrupt enable r/w received sa6 = 1000 interrupt enable: when this bit is 0: the received sa6 = 1000 interrupt is disabled. when this bit is 1: the received sa6 = 1000 interrupt is enabled. 2 received sa6 = 001x interrupt enable r/w received sa6 = 001x interrupt enable: when this bit is 0: the received sa6 = 001x interrupt is disabled. when this bit is 1: the received sa6 = 001x interrupt is enabled.
xrt84l38 158 octal t1/e1/j1 framer rev. 1.0.1 1 received sa6 = others interrupt enable r/w received sa6 = others interrupt enable: when this bit is 0: the received sa6 = others interrupt is disabled. when this bit is 1: the received sa6 = others interrupt is enabled. 0 received sa6 = 0000 interrupt enable r/w received sa6 = 0000 interrupt enable: when this bit is 0: the received sa6 = 0000 interrupt is disabled. when this bit is 1: the received sa6 = 0000 interrupt is enabled. b it n umber b it n ame b it t ype b it d escription
xrt84l38 159 rev. 1.0.1 octal t1/e1/j1 framer . t able 9: pmon t1/e1 r eceive l ine c ode ( bipolar ) v iolation c ounter r egister 303 pmon r eceive l ine c ode ( bipolar ) v iolation c ounter (rlcvcmsb) h ex a ddress : 0 x n8, 0 x 00 b it f unction t ype d efault d escription -o peration 7-4 unused ro 0 3-0 rxlcv count - high byte rur 0 these four reset upon read bits along with pmon receive line code vio - lation counter - lsb, provides a 12-bit representation of the number of line code violations that have been detected by the receive framer block since the last read of these registers. lower 8 bits. this register contains the lowest four bits within this 12 bit expression t able 10: pmon t1/e1 r eceive l ine c ode ( bipolar ) v iolation c ounter r egister 304 pmon r eceive l ine c ode ( bipolar ) v iolation c ounter (rlcvclsb) h ex a ddress : 0 x n8, 0 x 01 b it f unction t ype d efault d escription -o peration 7-0 rxlcv count - low byte rur 0 these eight reset upon read bits along with pmon receive line code violation counter - msb, provides 12-bit representation of the number of line code violations that have been detected by receive framer block since the last read of these registers. upper 4 bits. this register contains the upper 8 bits within this 12 bit expression. t able 11: pmon t1/e1 r eceive f raming a lignment b it e rror c ounter r egister 305 pmon r eceive f raming a lignment e rror c ounter (rfaeclsb) h ex a ddress : 0 x n8, 0 x 02 b it f unction t ype d efault d escription -o peration 7-0 framing alignment error count - high byte rur 0 these eight reset upon read bits along with pmon e1 receive framing alignment bit error counter- lsb, provides a 12-bit representation of the number of framing alignment errors that have been detected by receive e1 framer number n since the last read of these registers. this register contains the upper 8bits within this 12-bit expression. t able 12: pmon t1/e1 r eceive f raming a lignment b it e rror c ounter r egister 306 pmon r eceive f raming a lignment b it e rror c ounter (rfab-ecmsb) h ex a ddress : 0 x n8, 0 x 03 b it f unction t ype d efault d escription -o peration 7-4 unused r/o 0 3-0 framing alignment error count - low byte rur 0 these four reset upon read bits along with pmon e1 receive framing alignment bit error counter- msb, provides 12-bit representation of the number of framing alignment errors that have been detected by receive e1 framer block since the last read of these register. this register contains the lowest four bits within this 12-bit expression
xrt84l38 160 octal t1/e1/j1 framer rev. 1.0.1 t able 13: pmon t1/e1 r eceive s everely e rrored f rame c ounter r egister 307 pmon r eceive s everely e rrored f rame c ounter (rsefc) h ex a ddress : 0 x n8, 0 x 04 b it f unction t ype d efault d escription -o peration 7-0 severely errored frame count rur 0 severely errored 8-bit frame accumulation counter note: a severely errored frame event is defined as the occurrence of two consecutive errored frame alignment signals that are not responsi - ble for loss of frame alignment. t able 14: pmon t1/e1 r eceive crc-4 b lock e rror c ounter - msb r egister 308 pmon r eceive s ynchronization b it b lock e rror c ounter (rsbbecmsb) h ex a ddress : 0 x n8, 0 x 05 b it f unction t ype d efault d escription -o peration 7-0 crc-4 block error count - high byte rur 0 these eight reset upon read bits along with pmon e1 receive crc-4 block error counter - lsb, provides a 10-bit representation of the number of crc-4 block errors detected by receive e1 framer block since the last read of these registers. this register contains the upper eight bits of this 10 bit expression t able 15: pmon t1/e1 r eceive crc-4 b lock e rror c ounter - lsb r egister 309 pmon r eceive s ynchronization b it b lock e rror c ounter (rsbbeclsb) h ex a ddress : 0 x n8, 0 x 06 b it f unction t ype d efault d escription -o peration 7-2 unused ro 0 1-0 crc-4 block error count - low byte rur 0 these two reset upon read bits along with pmon e1 receive crc-4 block error counter - msb, provides a 10-bit representation of the number of crc-4 block errors that have been detected by a receive e1 framer block since the last read of these registers. this register contains the lower two bits within this 10 bit expression. note: counter contains the 10-bit synchronization bit error event. a synchro - nization bit error event is defined as a crc-4 error received. counter is dis - abled during loss of sync at either the frame/fas or esf/crc4 level, but it will not be disabled if loss of multiframe sync occurs at the cas level. t able 16: pmon t1/e1 r eceive f ar -e nd bl ock e rror c ounter - msb r egister 310 pmon r eceive f ar -e nd b lock e rror c ounter (e1rfebecmsb) h ex a ddress : 0 x n8, 0 x 07 b it f unction t ype d efault d escription -o peration 7-0 far-end block error count - high byte rur 0 these eight reset upon read bits along with pmon e1 receive far-end block error counter - lsb, provides a 10-bit representation of the number of far end block error events that have been detected by the receive e1 framer block since the last read of these registers. this register contains the upper eight bits within this 10 bit expression.
xrt84l38 161 rev. 1.0.1 octal t1/e1/j1 framer t able 17: pmon t1/e1 r eceive f ar e nd b lock e rror c ounter r egister 311 pmon r eceive f ar e nd b lock e rror c ounter (rfebeclsb) h ex a ddress : 0 x n8, 0 x 08 b it f unction t ype d efault d escription -o peration 7-2 unused ro 0 1-0 far-end block error count -low byte rur 0 these two reset upon read bits along with pmon e1 receive far-end block error counter - msb, provides a 10-bit representation of the number of far end block error events that have been detected by the receive e1 framer block since the last read of these registers. this register contains the lower two bits within this 10 bit expression. note: counter contains the 10-bit far-end block error event. counter will increment once each time the received e-bit is set to zero. the counter is disabled during loss of sync at either the fas or crc-4 level and it will continue to count if loss of multiframe sync occurs at the cas level. t able 18: pmon t1/e1 r eceive s lip c ounter r egister 312 pmon r eceive s lip c ounter (rsc) h ex a ddress : 0 x n8, 0 x 09 b it f unction t ype d efault d escription -o peration 7-0 slip count rur 0 note: counter contains the 8-bit receive buffer slip event. a slip event is defined as a replication or deletion of a t1/e1 frame by the receiving slip buffer. note: a 12 bit counter which counts the occurrence of a bipolar viola - tion on the receive data line. this counter is of sufficient length so that the probability of counter saturation over a one second interval at a 10 -3-bit error rate (ber) is less than 0.001%. t able 19: pmon t1/e1 r eceive l oss of f rame c ounter r egister 313 pmon r eceive l oss of f rame c ounter (rlfc) h ex a ddress : 0 x n8, 0 x 0a b it f unction t ype d efault d escription -o peration 7-0 loss of frame counts rur 0 note: lofc is a count of the number of times a "loss of fas frame" has been declared. this counter provides the capability to measure an accumulation of short failure events.
xrt84l38 162 octal t1/e1/j1 framer rev. 1.0.1 t able 20: pmon t1/e1 r eceive c hange of f rame a lignment c ounter r egister 314 pmon r eceive c hange of f rame a lignment c ounter (rcfac) h ex a ddress : 0 x n8, 0 x 0b b it f unction t ype d efault d escription -o peration 7-0 cofa count rur 0 change of frame alignment accumulation counter. note: cofa is declared when the newly-locked framing is different from the one offered by off-line framer. t able 21: pmon lapd t1/e1 f rame c heck s equence e rror c ounter r egister 315 pmon lapd f rame c heck s equence e rror c ounter (fcsec) h ex a ddress : 0 x n8, 0 x 0c b it f unction t ype d efault d escription -o peration 7-0 fcs error count rur 0 frame check sequence error accumulation counter. note: counter accumulates the times of occurrence of receive frame check sequence error detected by lapd controller. t able 22: t1/e1 prbs b it e rror c ounter msb r egister 316 t1/e1 prbs b it e rror c ounter msb h ex a ddress : 0 x n8, 0 x 0d b it f unction t ype d efault d escription -o peration 7 prbse[15] rur 0 most significant bits of prbs bit error accumulation counter 6 prbse[14] rur 0 5 prbse[13] rur 0 4 prbse[12] rur 0 3 prbse[11] rur 0 2 prbse[10] rur 0 1 prbse[9] rur 0 0 prbse[8] rur 0
xrt84l38 163 rev. 1.0.1 octal t1/e1/j1 framer t able 23: t1/e1 prbs b it e rror c ounter lsb r egister 317 t1/e1 prbs b it e rror c ounter lsb h ex a ddress : 0 x n8, 0 x 0e b it f unction t ype d efault d escription -o peration 7 prbse[7] rur 0 least significant byte of prbs bit error accumulation counter. 6 prbse[6] rur 0 5 prbse[5] rur 0 4 prbse[4] rur 0 3 prbse[3] rur 0 2 prbse[2] rur 0 1 prbse[1] rur 0 0 prbse[0] rur 0 t able 24: t1/e1 t ransmit s lip c ounter r egister 318 t1/e1 t ransmit s lip c ounter (t1/e1tsc) h ex a ddress : 0 x n8, 0 x 0f b it f unction t ype d efault d escription -o peration 7 txslip[7] rur 0 slip accumulation counter. 6 txslip[6] rur 0 5 txslip[5] rur 0 4 txslip[4] rur 0 3 txslip[3] rur 0 2 txslip[2] rur 0 1 txslip[1] rur 0 0 txslip[0] rur 0
xrt84l38 164 octal t1/e1/j1 framer rev. 1.0.1 1.7 the interrupt structure within the framer the xrt84l38 framer is equipped with a sophisticated interrupt servicing structure. this interrupt structure includes an interrupt request output pin int , numerous interrupt enable registers and numerous interrupt status registers. the interrupt servicing structure, within the xrt84l38 framer contains three levels of hierarchy: ? the framer level ? the block level ? the source level. the framer interrupt structure has been carefully designed to allow the user to quickly determine the exact source of this interrupt (with minimal latency) which will aid the c/ p in determining the which interrupt service routine to call up in order to eliminate or properly respond to the condition(s) causing the interrupt. the xrt84l38 framer comes equipped with registers to support the servicing of this wide array of potential "interrupt request" sources. ta ble 25 lists the possible conditions that can generate interrupts. general flow of interrupt servicing when any of the conditions presented in table 25 occur, (if their interrupt is enabled), then the framer generates an interrupt request to the p/ c by asserting the active-low interrupt request output pin, int . shortly after the local c/ p has detected the activated int signal, it will enter into the appropriate user- supplied interrupt service routine. the first task for the p/ c, while running this interrupt service routine, may t able 25: l ist of the p ossible c onditions that can g enerate i nterrupts , in each f ramer i nterrupt b lock i nterrupting c ondition framer level loss of rxlineclk signal one second interrupt hdlc controller block transmit hdlc - start of transmission receive hdlc - start of reception transmit hdlc - end of transmission receive hdlc - end of reception fcs error receipt of abort sequence receipt of idle sequence slip buffer block slip buffer full slip buffer empty slip buffer - slip alarm & error block receipt of cas multi-frame yellow alarm detection of loss of signal condition detection of line code violation change in receive loss of framer condition change in receive ais condition receipt of fas frame yellow alarm t1/e1 frame block change in cas multi-frame alignment change in national bits change in cas signaling bits change in fas frame alignment change in the "in frame" condition detection of "frame mimicking data" detection of sync (crc-4/crc-6) errors detection of framing bit errors
xrt84l38 165 rev. 1.0.1 octal t1/e1/j1 framer be to isolate the source of the interrupt request down to the device level (e.g, the framer ic), if multiple peripheral ics exist in the user's system. however, once the interrupting peripheral device has been identified, the next task for the p/ c is to determine exactly what feature of functional section within the device requested the interrupt. determine the framer(s) requesting the interrupt if the interrupting device turns out to be the framer, then the p/ c must determine which of the eight framer channels requested the interrupt. hence, upon reaching this state, one of the very first things that the p/ c must do within the user framer interrupt service routine, is to perform a read of each of the block interrupt status registers within all of the framer channels that have been enabled for interrupt generation via their respective interrupt control registers. table 26 lists the indirect address for the block interrupt status registers associated with each of the framer channels within the framer. the bit-format of each of these block interrupt status registers is listed below. t able 26: a ddress of the b lock i nterrupt s tatus r egisters f ramer n umber a ddress of b lock i nterrupt s tatus r egister 0 0x0a, 0x02 1 0x1a, 0x02 2 0x2a, 0x02 3 0x3a, 0x02 4 0x4a, 0x02 5 0x5a, 0x02 6 0x6a, 0x02 7 0x7a, 0x02
xrt84l38 166 octal t1/e1/j1 framer rev. 1.0.1 t able 27: b lock i nterrupt s tatus r egister r egister 319 b lock i nterrupt s tatus r egister (bisr) h ex a ddress : 0 x na, 0 x 00 b it f unction t ype d efault d escription -o peration 7 sa6 ro 0 sa6 interrupt status 7-6 lbcode ro 0 loopback code interrupt 5 rxclklos rur 0 rxclk los interrupt status indicates if framer n has experienced a loss of recovered clock interrupt since last read of this register. 0 = loss of recovered clock interrupt has not occurred since last read of this register 1 = loss of recovered clock interrupt has occurred since last read of this register. 4 onesec rur 0 one second interrupt status indicates if the xrt84l38 has experienced a one second interrupt since the last read of this register. 0 = no outstanding one second interrupts awaiting service 1 = outstanding one second interrupt awaits service 3 hdlc ro 0 hdlc block interrupt status indicates if the hdlc block has an interrupt request awaiting service. 0 = no outstanding interrupt requests awaiting service 1 = hdlc block has an interrupt request awaiting service. interrupt service routine should branch to and read data link status register (address xa,06). n ote : this bit-field will be reset to 0 after the microprocessor has performed a read to the data link status register. 2 slip ro 0 slip buffer block interrupt status indicates if the slip buffer block has any outstanding interrupt requests awaiting service. 0 = no outstanding interrupts awaiting service 1 = slip buffer block has an interrupt awaiting service. interrupt service rou - tine should branch to and read slip buffer interrupt status register (address 0xxa,0x09. n ote : this bit-field will be reset to 0 after the microprocessor has performed a read of the slip buffer interrupt status register. 1 alarm ro 0 alarm & error block interrupt status indicates if the alarm & error block has any outstanding interrupts that are awaiting service. 0 = no outstanding interrupts awaiting service 1 = alarm & error block has an interrupt awaiting service. interrupt serstatus register (address xa,02) n ote : this bit-field will be reset to 0 after the microprocessor has performed a read of the alarm & error interrupt status register. 0 t1/e1 frame ro 0 t1/e1 framer block interrupt status indicates if an t1/e1 frame status interrupt request is awaiting service. 0 = no t1/e1 frame status interrupt is pending 1 = t1/e1 framer status interrupt is awaiting service.
xrt84l38 167 rev. 1.0.1 octal t1/e1/j1 framer for a given framer, the block interrupt status register presents the interrupt request status of each interrupt block within the framer. the block interrupt status register helps the p/ c identify which interrupt block(s) have requested the interrupt. whichever bit(s) are asserted in this register identifies which block(s) have experienced an interrupt generating condition, as presented in table 27 . once the p/ c has read this register, it can determine which branch within the interrupt service routine that it must follow in order to properly service this interrupt. the framer ic further supports the interrupt block hierarchy by providing the block interrupt enable register. the bit-format of this register is identical to that for the block interrupt status register and is presented below. the block interrupt enable register permits the user to individually enable or disable the interrupt requesting capability of each of the "interrupt blocks" within the framer. if a particular bit-field, within this register contains the value "0"; then the corresponding functional block has been disabled from generating any interrupt requests. 1.7.1 configuring the interrupt system, at the framer level the xrt84l38 framer ic permits the user to enable or disable each of the eight framers for interrupt generation. further, the chip permits the user to make the following configuration selection. 1. whether the source-level interrupt status bits are reset-upon-read or write-to-clear. 2. whether or not an activated interrupt is automatically cleared. 1.7.1.1 enabling/disabling the framer for interrupt generation each of the eight (8) framers of the xrt84l38 framer can be enabled or disabled for interrupt generation. this selection is made by writing the appropriate ?0? or ?1? to bit 0 (intrup_en) of the interrupt control register corresponding to that framer, (see table 29 ). t able 28: b lock i nterrupt e nable r egister r egister 320 b lock i nterrupt e nable r egister (bier) h ex a ddress : 0 x na, 0 x 01 b it f unction t ype d efault d escription -o peration 7 sa6_enb r/w 0 sa6 interrupt enable 6 lbcode_enb r/w 0 loopback code interrupt enable 5 rxclkloss r/w 0 rxlineclk loss interrupt enable 0 = disables interrupt 1 = enables interrupt 4 onesec_enb r/w 0 one second interrupt enable 0 = disables interrupt 1 = enables interrupt 3 hdlc_enb r/w 0 hdlc block interrupt enable 0 = disables all hdlc block interrupts 1 = enables hdlc block (for interrupt generation) at the block level 2 slip_enb r/w 0 slip buffer block interrupt enable 0 = disables all slip buffer block interrupts 1 = enables slip buffer block at the block level 1 alarm_enb r/w 0 alarm & error block interrupt enable 0 = disables all alarm & error block interrupts 1 = enables alarm & error block at the block level 0 t1/e1frame_enb r/w 0 t1/e1 frame block enable 0 = disables all frame block interrupts 1 = enables the frame block at the block level
xrt84l38 168 octal t1/e1/j1 framer rev. 1.0.1 n ote : setting this bit-field to "1" does not enable all of the interrupts within the framer. a given interrupt must also be enabled at the block and source-level before it is enabled for interrupt generation. 1.7.1.2 configuring the interrupt status bits within a given framer to be reset-upon-read or write-to-clear. the xrt84l38 source-level interrupt status register bits can be configured to be either reset-upon-read or write-to-clear. if the user configures the interrupt status registers to be reset-upon-read, then when the p/ c is reading the interrupt status register, the following happens: 1. the contents of the source-level interrupt status register automatically is reset to ?0x00" following the read operation. 2. the interrupt request output pin ( int ) automatically toggles false, or "high", upon reading the interrupt status register containing the last activated interrupt status bit. if the user configures the interrupt status registers to be write-to-clear, then when the p/ c is reading the interrupt status register, the following happens. 1. the contents of the source-level interrupt status register is not cleared to "0x00" following the read oper - ation. the p/ c has to write 0x00 to the interrupt status register in order to reset the contents of the reg - ister to 0x00. 2. reading the interrupt status register, which contains the activated bit(s) does not cause the interrupt request output pin ( int ) to toggle false. the interrupt request output pin does not toggle false until the p/ c has written 0x00 into this register. the interrupt service routine must include this write operation. the interrupt status register associated with a given framer can be configured to be either reset-upon-read or write-to-clear by writing the appropriate value into bit 2 within the interrupt control register (see table 29 ). 1.7.1.3 automatic reset of interrupt enable bits occasionally, the user's system which includes the fr amer, may experience a fault condition, such that a framer interrupt condition continuously exists. if this particular interrupt has been enabled, then the framer will generate an interrupt request to the p/ c. afterwards, the p/ c attempts to service this interrupt by reading the appropriate block-level and source-level interrupt status register. additionally, the local p/ c attempts to perform some system-related tasks in order to try to resolve these conditions causing the interrupt. after the local c/ p has attempted all of these things, the framer negates the int output pin. however, because this system fault still remains, the condition causing the framer to issue this interrupt also exists. consequently, the framer generates another interrupt request which forces the p/ c to once again attempt to service this interrupt. this results in the local p/ c being tied up in a continuous cycle of executing this one t able 29: i nterrupt c ontrol r egister r egister 26 i nterrupt c ontrol r egister (icr) h ex a ddress : 0 x n0, 0 x 1a b it m ode f unction t ype d efault d escription -o peration 7-3 unused ro 0 2 int_wc_rur r/w 0 interrupt write-to-clear or reset-upon-read select configures interrupt status bits to either rur or write-to-clear 0=interrupt status bit rur 1=interrupt status bit write-to-clear 1 enbclr r/w 0 interrupt enable auto clear 0=interrupt enable bits are not cleared after status reading 1=interrupt enable bits are cleared after status reading 0 intrup_enb r/w 0 interrupt enable for framer_n enables framer n for interrupt generation. 0 = disables corresponding framer block for interrupt generation 1 = enables corresponding framer block for interrupt generation
xrt84l38 169 rev. 1.0.1 octal t1/e1/j1 framer interrupt service routine. consequently, the p/ c, along with portions of the overall system, now becomes non-functional. to prevent this from occurring, the framer can be configured to automatically reset the interrupt enable bits following their activation by writing the appropriate value to bit 1 of the interrupt control register (see table 29 ). writing a "1" to this bit-field configures the framer to reset a given interrupt following activation. writing a "0" to this bit-field configures the framer to leave the interrupt enabled, following its activation.
xrt84l38 170 octal t1/e1/j1 framer rev. 1.0.1 2.0 the e1 framing structure 2.1 the single e1 frame a single e1 frame consists of 256 bits which is created 8000 times a second; thereby yielding a bit-rate of 2.048mbps. the 256 bits within each e1 frame is grouped into 32 octets or timeslots. these timeslots are numbered from 0 to 31. figure 17 presents a diagram of a single e1 frame. a single e1 frame consists of 32 timeslots. however, not all of these timeslots are available to transmit voice or user data. for instance, timeslot 0 is always reserved for system use and timeslot 16 is sometimes used (reserved) by the system. hence, within each e1 frame, either 30 or 31 of the 32 timeslots are available for transporting user or voice data. t imeslot 0 in general, there are two types of e1 frames. ? fas (frame alignment signaling) frames ? non-fas frames in any e1 data stream, the e1 frame type alternates between the fas and non-fas frames. the timeslot 0 octet within the fas e1 frame contains a framing alignment pattern and therefore supports framing. the timeslot 0 octet within the non-fas e1 frame contains bits that support signaling or data link message transmission. t imeslot 0 octets within fas frames the bit-format of a timeslot 0 octet within a fas frame is presented in table 30 . f igure 17. s ingle e1 f rame d iagram t able 30: b it f ormat of t imeslot 0 octet within a fas e1 f rame b it 7654321 0 value 1 1 0 1 1 0 0 si function frame alignment signaling (fas) pattern international bit d escription - o peration the fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) is used by the receive e1 framer at the remote terminal for frame synchronization/alignment purposes. in practice, the si bit within the fas e1 frame carries the results of a crc-4 calculation, which is discussed in greater detail in section 2.2.1 . timeslot 0 timeslot 1 timeslot 29 0 1 2 3 4 5 6 7 timeslot 30 timeslot 31 e1 frame
xrt84l38 171 rev. 1.0.1 octal t1/e1/j1 framer the table above indicates that the fas frame timeslot 0 octet consists of a single international bit within bit- field 0, si, followed by a fixed 7-bit pattern within bit-fields 1 through 7. b it 0?s i (i nternational b it ) the si bit within the fas e1 frame typically carries the results of a crc-4 calculation, which is discussed in greater detail in section 2.2.1 . the fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) will be used by the receive e1 framer at the remote terminal for frame synchronization/alignment purposes. section discusses how the receive e1 framer uses these bits. timeslot 0 octets within non-fas frames the bit-format of a timeslot 0 octet within a non-fas frame is presented in table 31 . the table above indicates the non-fas frame timeslot 0 octet consists of a single international bit, si, within bit- field 0. b it 0?s i (i nternational b it ) the si bit, within the non-fas e1 frame carries a specific value that will be used by the receive e1 framer, for crc multi-frame alignment purposes. section 7 discusses the exact role of the si bit-field within the non-fas frames. b it 1?f ixed at ?1? bit-field ?1? contains a fixed value ?1?. this bit-field will be used for fas framing synchronization/alignment purposes by the remote receive e1 framer. section _ discusses how the receive e1 framer uses this bit- field. b it 2?a (fas f rame y ellow a larm b it ) this bit-field is used to transmit a yellow alarm to the remote terminal. this bit-field is set to ?0? during normal conditions, and is set to ?1? whenever the receive e1 framer detects an los (loss of signal) or lof (loss of framing) condition in the incoming e1 frame data. b it 3 through 7?s a 4?s a 8 (n ational b its ) these bit-fields can be used to carry data link information from the local transmitting terminal to the remote receiving terminal. since the national bits only exist in the non-fas frames, they offer a maximum signaling data link bandwidth of 20kbps. 2.2 the e1 multi-frame structures the 84l38 octal framer supports two kinds of e1 multi-frame structures: ? crc multi-frame t able 31: b it f ormat of t imeslot 0 octet within a n on -fas e1 f rame b it 76543 2 1 0 value sa8 sa7 sa6 sa5 sa4 a 1 si function6 national bits yellow alarm fixed value international bit description- operation national bits these bit-fields can be used to carry data link information from the local transmitting terminal to the remote receiving terminal. since the national bits only exist in the non-fas frames, they offer a maximum signaling data link bandwidth of 20kbps. fas frame yellow alarm bit this bit-field is used to transmit a yellow alarm to the remote terminal. this bit-field is set to ?0? during normal conditions, and is set to ?1? whenever the receive e1 framer detects an los (loss of signal) or lof (loss of framing) condition in the incoming e1 frame data. fixed at ?1? bit-field ?1? contains a fixed value ?1?. this bit- field will be used for fas framing synchronization/ alignment purposes by the remote receive e1 framer. international bit the si bit within the non-fas e1 frame typically carries a specific value that will be used by the receive e1 framer for crc multi-frame alignment purposes.
xrt84l38 172 octal t1/e1/j1 framer rev. 1.0.1 ? cas multi-frame 2.2.1 the crc multi-frame structure a crc multi-frame consists of 16 consec utive e1 frames, with the first of these frames being a fas frame. from a frame alignment point of view, the timeslot 0 octets of each of these e1 frames within the multi-frame are the most important 16 octets. table 32 presents the bit-format for all timeslot 0 octets within a 16 frame crc multi-frame. table 32 has the crc multi-frame divided into 2 sub multi- frames. sub-multi-frame 1 is designated as smf1 and sub-multi-frame 2 is designated as smf2. smf1 consists of e1 frames 0 through 7 consisting of 4 fas frames and 4 non-fas frames. there are two interesting things to note in table 32 . first, all of the bit-field 0 positions within each of the fas frames are designated as c1, c2, c3 and c4. these four bit-fields contain the crc-4 values which has been computed over the previous smf. hence, while the transmit e1 framer is assembling a given smf, it computes the crc-4 value for that smf and inserts these results into the c1 through c4 bit-fields within the very next smf. these crc-4 values ul timately are used by the remote re ceive e3 framer for error-detection purposes. n ote : this framing structure is referred to as a crc multi-frame because it permits the remote receiving terminal to locate and verify the crc-4 bit-fields. the second interesting thing to note regarding table 32 is that the bit-field 0 positions within each of the non- fas frames are of a fixed six (6) bit pattern: 0, 0, 1, 0, 1, 1; along with two bits, each designated at ?e?. this six bit pattern is referred to as the crc multi-frame alignmen t pattern. this six-bit pattern will ultimately be used by the remote receive e1 framer for crc multi-frame synchronization/alignment. section discusses how the receive e1 framer uses this 6-bit crc multi-frame alignment pattern for frame synchronization/alignment. the "e" bits are used to indicate that the local receive e1 framer has detected errored sub-multi-frames. 2.2.2 cas multi-frames and channel associated signaling t able 32: b it f ormat of all t imeslot 0 octets within a crc m ulti - frame smf f rame n umber b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 c1 0 0 1 1 0 1 1 1 0 1 a sa4 sa5 sa6 sa7 sa8 2 c2 0 0 1 1 0 1 1 3 0 1 a sa4 sa5 sa6 sa7 sa8 4 c3 0 0 1 1 0 1 1 5 1 1 a sa4 sa5 sa6 sa7 sa8 6 c4 0 0 1 1 0 1 1 7 0 1 a sa4 sa5 sa6 sa7 sa8 2 8 c1 0 0 1 1 0 1 1 9 1 1 a sa4 sa5 sa6 sa7 sa8 10 c2 0 0 1 1 0 1 1 11 1 1 a sa4 sa5 sa6 sa7 sa8 12 c3 0 0 1 1 0 1 1 13 e 1 a sa4 sa5 sa6 sa7 sa8 14 c4 0 0 1 1 0 1 1 15 e 1 a sa4 sa5 sa6 sa7 sa8
xrt84l38 173 rev. 1.0.1 octal t1/e1/j1 framer cas multi-frames are only relevant if the user is using cas or channel associated signaling. if the user is implementing common channel signaling then the cas multi-frame is not available. the exact role of cas multi-frames is discussed in some detail in the next section. 2.2.2.1 channel associated signaling if the user operates an e1 channel in channel associated signaling (cas) mode, then the timeslot 16 octets within each e1 frame will be reserved for signaling. such signaling would convey information such as on- hook, off-hook conditions, call set-up, control, etc. in cas, this type of signaling data that is associated with a particular voice channel will be carried within timeslot 16 of a particular e1 frame within a cas multi-frame. the cas is carried in a multi-frame structure which consists of 16 consecutive e1 frames. the framing/byte format of a cas multi-frame is presented in figure 18 . figure 18 indicates that timeslot 16 within frame 1 of the cas multi-frame, contains 4 bits of signaling data for voice channel 1 and 4 bits of signaling data for voice channel 17. likewise, timeslot 16 within frame 2 contains 4 bits of signaling data for voice channel 2 and 4 bits of signaling data for voice channel 18; and so on. timeslot 16 within frame 0 is a special octet that is used for two purposes. 1. to convey cas multi-frame alignment information, and 2. to convey multi-frame alarm information to the remote terminal. the bit-format of timeslot 16 within frame 0 of a cas multi-frame is 0000 xyxx. the upper nibble of this octet contains all zeros and is used to identify itself as the cas multi-frame alignment signal. if cas is used, then the user is advised to insure that none of the other timeslot 16 octets contain the value "0000". the lower nibble of this octet contains the expression "xyxx". in this case, the x-bits are the spare bits and should be set to "0" if not used. the y-bit is used to indicate a multi-frame alarm condition to the remote terminal. during normal operation, this bit-field is cleared to "0". however, if the local receive e1 framer detects a problem with the incoming multi-frames, then the local transmit e1 framer will set this bit- field within the next outbound cas multi-frame to "1". f igure 18. f rame /b yte f ormat of the cas m ulti -f rame s tructure frame 0 frame 1 frame 2 frame 15 0000 xyxx timeslot 16 timeslot 16 timeslot 16 timeslot 16 abcd abcd signaling data associated with timeslot 1 signaling data associated with timeslot 17 abcd abcd abcd abcd cas multiframe alignment pattern x = ?dummy bits? y = carries the multiframe ?yellow alarm? bit signaling data associated with timeslot 2 signaling data associated with timeslot 18 signaling data associated with timeslot 15 signaling data associated with timeslot 31 a single cas multiframe
xrt84l38 174 octal t1/e1/j1 framer rev. 1.0.1 n ote : the local transmit e1 framer will continue to set the y-bit to "1" for the duration that the local receive e1 framer detects this problem. 2.2.2.2 common channel signaling (ccs) common channel signaling is an alternative form of signaling from channel associated signaling. in ccs, whatever signaling data which is transported via the outbound e1 data stream, carries information that applies to all of the voice channels as a set (e.g., timeslots 1 through 15 and 17 through 31) in the e1 frame. there are numerous other variations of common channel signaling that are available. some of these are listed below. ? 31 voice channels with the common channel signaling being transported via the national bits. ? 30 voice channels with the common channel signaling data being transported via the national bits and cas data being transported via timeslot 16. ? 30 voice channels with the common channel signaling being processed via timeslot 16. (e.g., primary rate isdn signaling). a more detailed discussion of these forms of common channel signaling are discussed in section 10.0. f igure 19. e1 f rame f ormat fr 0 fr 1 fr 2 fr 3 fr 4 fr 5 fr 6 fr 15 fr 14 fr 13 fr 12 fr 11 fr 10 fr 9 fr 8 fr 7 1 n n n n n a 1 a d c b a d c b 1 8 7 6 5 4 3 2 1 1 1 0 1 1 0 0 0 x x y x 0 0 0 ts 0 ts 1 ts 2 ts 15 ts 31 ts 30 ts 29 ts 18 - 28 ts 17 ts 16 ts 3 - 14 fas mas time slot 16 time slot 0 time slots 1-15, 17-31 channel data b. frames 1-15 b. odd frames 1, 3, 5-15 a. even frames 0, 2, 4-14 a. frame 0 8 bits/ time slot 32 time slots/frame 16 frames/ multiframe
xrt84l38 175 rev. 1.0.1 octal t1/e1/j1 framer 3.0 the ds1 framing structure a single t1 frame is 193 bits long and is transmitted at a frame rate of 8000hz. this results in an aggregate bit rate of 193 bits x 8000/sec = 1.544 mbits/sec. basic frames are divided into 24 timeslots numbered 1 thru 24 and a framing bit, see figure 20 . each timeslot is 8 bits in length and is transmitted most significant bit first, numbered bit 0. this results in a single timeslot data rate of 8 bits x 8000/sec = 64 kbits/sec. 3.1 t1 super frame format (sf) the superframe format (sf), is also referred to as the d4 format. the requirement for associated signaling in frames 6 and 12 dictates that the frames be distinguishable. this leads to a multiframe structure consisting of 12 frames per superframe (sf). see figure 21 and ta ble 33 . the sf structure consists of a multiframe of 12 frames. each frame has 24 timeslots, plus an f-bit and 8 bits per timeslot. a timeslot is equivalent to one voice circuit or one 64kb/s data circuit. this structure of frames and multiframes is defined by the f-bit pattern. the f-bit is designated alternately as an ft bit (terminal framing bit) or fs bit (signalling framing bit). the ft bit carries a pattern of alternating zeros and ones (101010) in odd frames that defines the boundaries so that one timeslot may be distinguished from another. the fs bit carries a pattern of (001110) in even frames and defines the multiframe boundaries so that one frame may be distinguished from another. f igure 20. t1 f rame f ormat 125 s ds1 frame (8/1.544) s bit 0 bit 0 bit 1 bit 1 bit 2 bit 2 bit 3 bit 3 bit 4 bit 4 bit 5 bit 5 bit 6 bit 6 bit 7 bit 7 timeslot 24 s bit timeslots 2 - 22 s bit timeslot 23 timeslot 24 timeslot 1 timeslot 1 (1/1.544) s
xrt84l38 176 octal t1/e1/j1 framer rev. 1.0.1 f igure 21. t1 s uperframe pcm f ormat t able 33: s uperframe f ormat f rame b it f-b its b it u se in e ach t imeslot s ignalling c hannel t erminal f raming f t t erminal f raming f s t raffic s ig 1 0 1 ---- 1-8 ---- ---- 2 193 ---- 0 1-8 ---- ---- 3 386 0 ---- 1-8 ---- ---- 4 579 ---- 0 1-8 ---- ---- 5 772 1 ---- 1-8 ---- ---- 6 965 ---- 1 1-7 8 a 7 1158 0 ---- 1-8 ---- ---- 8 1351 ---- 1 1-8 ---- ---- 9 1544 1 ---- 1-8 ---- ---- 10 1737 ---- 1 1-8 ---- ---- 11 1930 0 ---- 1-8 ---- ---- 12 2123 ---- 0 1-7 8 b b a bit 0 bit 1 bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 8 bits per timeslot ft or fs ft or fs ts 1 ts 1 ts 2 ts 2 ------------------ ------------------ ts 13 ts 13 ------------------- ------------------- ts 24 ts 24 fr 1 fr 1 fr 2 fr 2 ------------------ ------------------ fr 7 fr 7 ------------------- ------------------- fr 11 fr 11 fr 12 fr 12 signalling information bit 7 during: frame 12 frame 6 24 timeslots per frame frame = 193 bits multiframe sf = 12 frames
xrt84l38 177 rev. 1.0.1 octal t1/e1/j1 framer 3.2 t1 extended superframe format in extended superframe format (esf), as shown in figure 22 and table 34 , the multiframe structure is extended to 24 frames. the timeslot structure is identical to d4 (sf) format. robbed-bit signaling is accommodated in frame 6 (a-bit), frame 12 (b-bit), frame 18 (c-bit) and frame 24 (d-bit). the f-bit pattern of esf contains three functions: 1. framing pattern sequence (fps), which defines the frame and multiframe boundaries. 2. facility data link (fdl), which allows data such as error-performance to be passed within the t1 link. 3. cyclic redundancy check (crc), which allows error performance to be monitored and enhances the reli - ability of the receiver?s framing algorithm. f igure 22. t1 e xtended s uperframe f ormat t able 34: e xtended s uperframe f ormat f rame b it f-b its b it u se in e ach t imeslot s ignalling c hannel fps dl crc t raffic s ig 16 4 2 1 0 ---- m ---- 1-8 ---- ---- ---- ---- 2 193 ---- ---- c1 1-8 ---- ---- ---- ---- 3 386 ---- m ---- 1-8 ---- ---- ---- ---- 4 579 0 ---- ---- 1-8 ---- ---- ---- ---- 5 772 ---- m ---- 1-8 ---- ---- ---- ---- d c crc crc fdl fdl b a bit 0 bit 1 bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 8 bits per timeslot fps or fs fps or fs ts 1 ts 1 ts 2 ts 2 ------------------ ------------------ ts 13 ts 13 ------------------- ------------------- ts 24 ts 24 fr 1 fr 1 fr 2 fr 2 ------------------ ------------------ fr 13 fr 13 ------------------- ------------------- fr 23 fr 23 fr 24 fr 24 signalling information bit 7 during: frame 24 frame 18 frame 12 frame 6 24 timeslots per frame frame = 193 bits multiframe esf = 12 frames
xrt84l38 178 octal t1/e1/j1 framer rev. 1.0.1 6 965 ---- ---- c2 1-7 8 a a a 7 1158 ---- m ---- 1-8 ---- ---- ---- ---- 8 1351 0 ---- ---- 1-8 ---- ---- ---- ---- 9 1544 ---- m ---- 1-8 ---- ---- ---- ---- 10 1737 ---- ---- c3 1-8 ---- ---- ---- ---- 11 1930 ---- m ---- 1-8 ---- ---- ---- ---- 12 2123 1 ---- ---- 1-7 8 b b b 13 2316 ---- m ---- 1-8 ---- ---- ---- ---- 14 2509 ---- ---- c4 1-8 ---- ---- ---- ---- 15 2702 ---- m ---- 1-8 ---- ---- ---- ---- 16 2895 0 ---- ---- 1-8 ---- ---- ---- ---- 17 3088 ---- m ---- 1-8 ---- ---- ---- ---- 18 3281 ---- ---- c5 1-7 8 c c a 19 3474 ---- m ---- 1-8 ---- ---- ---- ---- 20 3667 1 ---- ---- 1-8 ---- ---- ---- ---- 21 3860 ---- m ---- 1-8 ---- ---- ---- ---- 22 4053 ---- ---- c6 1-8 ---- ---- ---- ---- 23 4246 ---- m ---- 1-8 ---- ---- ---- ---- 24 4439 1 ---- ---- 1-7 8 d b a n otes : 1. fps indicates the framing pattern sequence (...001011...) 2. dl indicates the 4kb/s data link with message bits m. 3. crc indicates the cyclic redundancy check with bits c1 to c6 4. signaling options include 16 state, 4 state and 2 state. t able 34: e xtended s uperframe f ormat f rame b it f-b its b it u se in e ach t imeslot s ignalling c hannel fps dl crc t raffic s ig 16 4 2
xrt84l38 179 rev. 1.0.1 octal t1/e1/j1 framer 3.3 slc 96 format (slc) slc framing mode allows synchronization to the slc?96 data link pattern. this pattern described in the bellcore tr-tsy-000008, contains both signaling information and a framing pattern that overwrites the fs bit of the sf framer pattern. see ta ble 35 . t able 35: slc ? 96 f s b it c ontents f rame # fs b it f rame # fs b it f rame # fs b it 2 0 26 c2 50 0 4 0 28 c3 52 m1 6 1 30 c4 54 m2 8 1 32 c5 56 m3 10 1 34 c6 58 a1 12 0 36 c7 60 a2 14 0 38 c8 62 s1 16 0 40 c9 64 s2 18 1 42 c10 66 s3 20 1 44 c11 68 s4 22 1 46 0 70 1 24 c1 48 1 72 0 n otes : 1. the slc ? 96 frame format is similar to that of sf as shown in table 33 with the exceptions shown in this table. 2. c1 to c11 are concentrator bit fields. 3. m1 to m3 are maintenance bit fields. 4. a1 and a2 are alarm bit fields. 5. s1 to s4 are line switch bit fields. 6. the fs bits in frames 46, 48 and 70 are spoiler bitswhich are used to protect against false mutiframing.
xrt84l38 180 octal t1/e1/j1 framer rev. 1.0.1 4.0 the ds1 transmit section 4.1 the ds1 transmit payload data input interface block 4.1.1 description of the transmit payload data input interface block each of the eight framers within the xrt84l38 includes a transmit payload data input interface block. the function of this block is to provide an interface to the local terminal equipment (for example, a central office or switching equipment) that has data to send to a far end terminal over a ds1 or e1 transport medium. the payload data input interface module (also known as the back-plane interface module) supports payload data to be taken from or presented to the system. in ds1 mode, supported data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. in e1 mode, supported data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the transmit payload data input interface block supplies or accepts the following signals to the local terminal equipment circuitry: ? transmit serial data input (txser_n) ? transmit serial clock (txserclk_n) ? transmit single-frame synchronization signal (txsync_n) ? transmit multi-frame synchronization signal (txmsync_n) ? transmit time-slot indicator clock (txtsclk_n) ? transmit time-slot indication bits (txtsb[4:0]_n) the transmit serial data is an input pin carrying payload, signaling and sometimes data link data supplied by the local terminal equipment to the xrt84l38. the transmit serial clock is an input or output signal used by the transmit payload data input interface block to latch in incoming serial data from the local terminal equipment. the transmit clock inversion bit of the transmit interface control register (ticr) determines at which edge of the transmit serial clock would data transition on the transmit serial data pin occur. the table below shows configurations of the transmit clock inversion bit of the transmit interface control register (ticr). throughout the discussion of this datasheet, we assume that serial data transition happens on the rising edge of the transmit serial clock unless stated otherwise. the transmit single-frame synchronization signal is either input or output. when configured as input, it indicates the beginning of a ds1 frame. when configured as output, it indicates the end of a ds1 frame. the transmit multi-frame synchronization signal is either input or output. when configured as input, it indicates the beginning of a ds1 multi-frame. when configured as output, it indicates the end of a ds1 multi-frame. the transmit input clock signal is multiplexed into the transmit multi-frame synchronization pin (txmsync_n) of xrt84l38. when the framer is running at high-speed back-plane interface mode, the transmit input clock functions as the timing source for the high-speed back-plane interface. transmit interface control register (ticr) (indirect address = 0xn0h, 0 x20h) b it n umber b it n ame b it t ype b it d escription 3 transmit clock inversion r/w 0 - serial data transition happens on rising edge of the transmit serial clock. 1 - serial data transition happens on falling edge of the transmit serial clock.
xrt84l38 181 rev. 1.0.1 octal t1/e1/j1 framer by connecting these signals with the local terminal equipment, the transmit payload data input interface accepts payload data from the terminal equipment and routes it to the transmit framer module inside the device. 4.1.2 brief discussion of the transmit payload data input interface block operating at 1.544mbit/s mode if the framer is operating in normal 1.544mbit/s back-plane interface mode for ds1, timing source of the transmit section can be one of the three clocks: ? transmit serial input clock ? oscclk driven divided clock ? recovered receive line clock the transmit timing source select [1:0] bits of the clock select register (csr) determine which clock is used as the timing source. the following table shows configurations of the transmit timing source select [1:0] bits of the clock select register. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 1-0 transmit timing source select r/w these two read/write bit-fields permit the user to select the timing source of transmit section of the framer. when the transmit back-plane interface is operating at a clock rate of 1.544mhz for t1, these two read/write bit-fields also determine the direction of single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk). when the framer is operating at other back-plane mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. 00 - the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. 01 - the transmit serial clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchro - nization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. 10 - the oscclk driven divided clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. 11 - the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 1.544mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer.
xrt84l38 182 octal t1/e1/j1 framer rev. 1.0.1 the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) can be either inputs or outputs depend on the timing source of the transmit section of the framer. with the oscclk driven divided clock or the recovered receive line clock being the timing source of the transmit section, the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) are all outputs. with the timing source of the transmit section being the transmit serial input clock, the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) are all inputs. the following table illustrates the input and output nature of these signals for different transmit timing sources. the transmit time-slot indication bits (txtsb[4:0]_n) are multiplexed i/o pins. the functionality of these pins is governed by the value of transmit fractional t1 input enable bit of the transmit interface control register (ticr). the following table illustrates the configurations of the transmit fractional ds1 input enable bit. when configured to operate in normal condition (that is, when the transmit fractional t1 input enable bit is equal to zero), these bits reflect the five-bit binary value of the time slot number (0 - 23) being accepted and processed by the transmit payload data input interface block of the framer. txtsb[4] represents the msb of the binary value and txtsb[0] represents the lsb. t able 36: s ignals for different t ransmit timing sources t ransmit t iming s ource t x s er c lk _ n t x s ync _ n t x ms ync _ n terminal equipment driven txserclk input input input oscclk driven divided clock output output output recovered receive line clock output output output transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 transmit fractional ds1 input enable r/w 0 - the transmit time-slot indication bits (txtsb[4:0] are outputting five-bit binary values of time-slot number (0-23) being accepted and processed by the transmit payload data input interface block of the framer. the transmit time-slot indicator clock signal (txtsclk_n) is a 192khz clock that pulses high for one ds1 bit period whenever the transmit payload data input interface block is accepting the lsb of each of the twenty-four time slots. 1 - the txtsb[0]_n bit becomes the transmit fractional t1 input signal (txfrtd_n) which carries fractional ds1 payload data into the framer. the txtsb[1]_n bit becomes the transmit signaling data input signal (txsig_n) which is used to insert robbed-bit signaling data into the outbound ds1 frame. the txtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-23) being accepted and processed by the transmit payload data input interface block of the framer. the txtsb[3]_n bit becomes the transmit overhead synchronization pulse (txohsync_n) which is used to output an overhead synchronization pulse that indicates the first bit of each ds1multi-frame. the txtsclk_n will output gaped fractional ds1 clock that can be used by ter - minal equipment to clock out fractional ds1 payload data at rising edge of the clock. or,the txtsclk_n pin will be a clock enable signal to transmit fractional ds1 input signal (txfrtd_n) when the un-gaped transmit serail input clock (txserclk_n) is used to clock in fractional ds1 payload data into the framer.
xrt84l38 183 rev. 1.0.1 octal t1/e1/j1 framer when the transmit fractional t1 input enable bit is equal to one, the txtsb[0]_n bit becomes the transmit fractional t1 input signal (txfrtd_n). this input pin carries fractional t1 input data to be inserted into the outbound ds1 data stream. the fraction t1 input interface allows certain time-slots of outbound ds1 data stream to have a different source other than the local terminal equipment. function of the fractional t1 input signal will be discussed in details in later sections. when the transmit fractional t1 input enable bit is equal to one, the txtsb[1]_n bit becomes the transmit signaling data input signal (txsig_n). these input pins can be used to insert robbed-bit signaling data into the outbound ds1 frame. function of the transmit signaling data input signal will be discussed in details in later sections. when the transmit fractional t1 input enable bit is equal to one, the txtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-23) being accepted and processed by the transmit payload data input interface block of the framer. msb of the binary value is presented first and the lsb is presented last. when the transmit fractional t1 input enable bit is equal to one, the txtsb[3]_n bit becomes the transmit overhead synchronization pulse (txohsync_n). these pins can be used to output an overhead synchronization pulse that indicates the first bit of each ds1multi-frame. function of the transmit overhead synchronization output signal will be discussed in details in later sections. the txtsb[4]_n bit is not multiplexed. the table below shows functionality of the txtsb[3:0] bits when the transmit fractional t1 input bit is set to different values. the transmit time-slot indicator clock signal (txtsclk_n) is a multi-function output pin. when configured to operate in normal condition (that is, when the transmit fractional t1 input enable bit is equal to zero), the txtsclk_n is a 192khz clock that pulses high for one ds1 bit period whenever the transmit payload data input interface block is accepting the lsb of each of the twenty-four time slots. the local terminal equipment should use this clock signal to sample the txtsb[0] through txtsb[4] bits and identify the time-slot being processed via the transmit section of the framer. when the transmit fractional t1 input enable bit is equal to one, the txtsclk_n will output gaped fractional ds1 clock at time-slots where fractional t1 input data is present. this clock can be used by terminal equipment to clock out fractional ds1 payload data at rising edge of the clock. the framer will then input fractional ds1 payload data using falling edge of the clock. otherwise, this pin can be configured as a clock enable signal to transmit fractional ds1 input signal (txfrtd_n) if the framer is set accordingly. in this way, fractional ds1 payload data is clocked into the framer using un-gaped transmit serail input clock (txserclk_n). a detailed discussion of the fractional ds1 payload data input interface can be found in later sections. both the transmit time-slot indicator clock (txtsclk_n) and the transmit time-slot indication bits (txtsbb[4:0]_n) are output signals in normal 1.544mbit/s back-plane mode regardless of the timing source of the transmit section of framer. 4.1.2.1 connect the transmit payload data input interface block to the local terminal equipment if transmit timing source = txserclk_n by setting the transmit timing source [1:0] bits of the clock select register to 01, the txserclk_n input signal is configured to be the timing source for the transmit section of the framer. the terminal equipment should supply an external free-running clock with frequency of 1.544mhz to the txserclk_n input pin. the transmit single- frame synchronization signal and the transmit multi-frame synchronization signal are inputs to the framer. t able 37: t he t x ts b [3:0] bits when the t ransmit f ractional t1 i nput bit is set to different values t ransmit f ractional t1 i nput b it = 0 t ransmit f ractional t1 i nput b it = 1 txtsb[0] output txfrtd input txtsb[1] output txsig input txtsb[2] output txts output txtsb[3] output txohsync output
xrt84l38 184 octal t1/e1/j1 framer rev. 1.0.1 the transmit single-frame synchronization signal should pulse ?high? for one ds1 bit period (648ns) at the framing bit position of each ds1 frame. by sampling the ?high? pulse on the transmit single-frame synchronization signal, the framer can position the beginning of a ds1 frame. the transmit multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the framing bit position of the first frame of a ds1 multi-frame. by sampling the high pulse on the transmit multi- frame synchronization signal, the framer can position the beginning of a ds1 super-frame. it is the responsibility of the terminal equipment to provide serial input data through the txser_n pin aligned with the transmit single-frame synchronization signal and the transmit multi-frame synchronization signal. see figure 23 below for how to connect the transmit payload data input interface block to the local terminal equipment with the transmit serial clock being the timing source of transmit section. f igure 23. i nterfacing xrt84l38 to local t erminal e quipment with t x s er c lk _ n as t ransmit t iming s ource txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 185 rev. 1.0.1 octal t1/e1/j1 framer figure 24 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connect the transmit payload data input interface block to the local terminal equipment with the transmit serial clock being the timing source of transmit section. 4.1.2.2 connect the transmit payload data input interface block to the local terminal equipment if the transmit timing source = oscclk by setting the transmit timing source [1:0] bits of the clock select register (csr) to 10, the oscclk driven divided clock is configured to be the timing source for the transmit section of the framer. a free-running clock should apply to the oscclk input pin with frequencies of 12.352mhz, 24.704mhz and 49.408mhz depending on the setting of oscclk frequency select [1:0] bits of the clock select register (csr). the free-running oscclk is divided inside the xrt84l38 and routed to all eight framers. this oscclk driven divided clock has to be 12.352mhz in frequency. when these bits are set to 00, the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 12.352mhz. when these bits are set to 01, the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 24.704mhz. when these bits are set to 10, the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 49.408mhz. the following table shows configurations of the oscclk frequency select [1:0] bits of the clock select register. f igure 24. w aveforms of the signals that connect the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the t ransmit s erial clock being the t iming s ource of the t ransmit s ection c txserclk txserclk (inv) txser txsync(input) txtsclk txtsb[4:0] txtsb[0]/txsig txtsb[4:0] txtsclk txtsb[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d
xrt84l38 186 octal t1/e1/j1 framer rev. 1.0.1 the transmit serial clock signal pin (txserclk_n) is output from the framer. the framer outputs a 1.544mhz clock through this pin to the local terminal equipment. the transmit single-frame synchronization signal and the transmit multi-frame synchronization signal are also automatically configured to be output signals. the transmit single-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of each ds1 frame. by triggering on the high pulse on the transmit single-frame synchronization signal, the local terminal equipment can identify the end of a ds1 frame and should start inserting payload data of the next ds1 frame to the framer. the transmit multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of the last frame of a ds1 multi-frame. by triggering on the high pulse on the transmit multi-frame synchronization signal, the local terminal equipment can identify the end of a ds1 super-frame and should start inserting payload data of the next ds1 multi-frame into the framer. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 3-2 oscclk frequency select r/w oscclk frequency select: these two read/write bit-fields permit the user to select internal clock divid - ing logic of the framer depending on the frequency of incoming oscillator clock (oscclk). the frequency of internal clock used by the framer should be 12.352mhz. 00 - the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 12.352mhz. 01 - the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 24.704mhz. 10 - the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 49.408mhz.
xrt84l38 187 rev. 1.0.1 octal t1/e1/j1 framer see figure 25 for how to connect the transmit payload data input interface block to the local terminal equipment with the oscclk driven divided clock as the timing source of transmit section. f igure 25. i nterfacing xrt84l38 to the local t erminal e quipment with the oscclk d riven d ivided c lock as t ransmit t iming s ource txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 oscclk oscclk driven divided clock
xrt84l38 188 octal t1/e1/j1 framer rev. 1.0.1 figure 26 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connect the transmit payload data input interface block to the local terminal equipment with the oscclk driven divided clock as the timing source of transmit section. 4.1.2.3 connect the transmit payload data input interface block to the local terminal equipment for loop-timing applications if the transmit timing source [1:0] bits of the clock select register are set to 00 or 11, the recovered receive line clock is configured to be the timing source for the transmit section of the framer. this is also known as the loop-timing mode. if the clock loss detection enable bit of the clock select register is set to one, and if the recovered receive line clock from the liu is lost, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. f igure 26. w aveforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the oscclk d riven d ivided clock as the timing source of the t ransmit s ection c txserclk txserclk (inv) txser txsync(output) txtsclk txtsb[4:0] txtsb[0]/txsig txtsclk txtsb[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d txtsb[0]/txsig
xrt84l38 189 rev. 1.0.1 octal t1/e1/j1 framer the following table shows configuration of the clock loss detection enable bit of the clock select register (csr). the transmit serial clock signal pin (txserclk_n) is output from the framer. the xrt84l38 routes the recovered receive line clock internally across the framer and output through the transmit serial clock signal pin to the local terminal equipment. the transmit single-frame synchronization signal and the transmit multi- frame synchronization signal are automatically configured to be output signals. the transmit single-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of each ds1 frame. by triggering on the high pulse on the transmit single-frame synchronization signal, the local terminal equipment can identify the end of a ds1 frame and should start inserting payload data of the next ds1 frame to the framer. the transmit multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of the last frame of a ds1 multi-frame. by triggering on the high pulse on the transmit multi-frame synchronization signal, the local terminal equipment can identify the end of a ds1 super-frame and should start inserting payload data of the next ds1 multi-frame into the framer. clock select register (csr) (indirect address = 0xn0h, 0 x00h) b it n umber b it n ame b it t ype b it d escription 4 clock loss detection enable r/w clock loss detection enable: this read/write bit-field permits the user to enable the clock loss detection logic for the framer when the recovered receive line clock is used as transmit timing source of the framer. 0 - the framer disables the clock loss detection logic. 1 - the framer enables the clock loss detection logic. if the recovered receive line clock is used as transmit timing source of the framer, and if clock recovered from the liu is lost, the framer can detect loss of the recovered receive line clock. upon detecting of this occurrence, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. n ote : this bit-field is ignored if the txserclk or the oscclk driven divided clock is chosen to be the timing source of transmit section of the framer.
xrt84l38 190 octal t1/e1/j1 framer rev. 1.0.1 see figure 27 for how to connect the transmit payload data input interface block to the local terminal equipment with the recovered receive line clock being the timing source of transmit section. f igure 27. i nterfacing xrt84l38 to local t erminal e quipment with r ecovered r eceive l ine c lock as t ransmit t iming s ource txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 rxlineclk_0 rxlineclk_7
xrt84l38 191 rev. 1.0.1 octal t1/e1/j1 framer the following figure 28 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connecting the transmit payload data input interface block to the local terminal equipment with the recovered receive line clock being the timing source of transmit section. 4.1.3 brief discussion of the transmit high-speed back-plane interface the high-speed back-plane interface supports payload data to be taken from or presented to the terminal equipment at a rate higher than 1.544mbit/s. in ds1 mode, supported high-speed data rates are mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the transmit multiplex enable bit and the transmit interface mode select [1:0] bits of the transmit interface control register (ticr) determine the transmit back-plane interface data rate. the following table shows configurations of the transmit multiplex enable bit and the transmit interface mode select [1:0] bits of the transmit interface control register (ticr). f igure 28. w aveforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the r ecovered r eceive l ine c lock being the timing source of the t ransmit s ection transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 2 transmit multiplex enable r/w 0 - the transmit back-plane interface block is configured to non-channel-multi - plexed mode. 1 - the transmit back-plane interface block is configured to channel-multiplexed mode 1-0 transmit interface mode select r/w when combined with the transmit multiplex enable bit, these bits determine the transmit back-plane interface data rate. c txserclk txserclk (inv) txser txsync(output) txtsclk txtsb[4:0] txtsb[0]/txsig txtsclk txtsb[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d txtsb[0]/txsig
xrt84l38 192 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the combinations of transmit multiplex enable bit and transmit interface mode select [1:0] bits and the resulting transmit back-plane interface data rates. when the transmit multiplex enable bit is set to zero, the framer is configured in non-channel-multiplexed mode. the possible data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s. in non-channel- multiplexed mode, payload data of each channel are taken from the terminal equipment separately. each channel uses its own transmit serial clock, transmit serial data, transmit single-frame synchronization signal and transmit multi-frame synchronization signal as interface between the framer and the terminal equipment. section 4.1.2.1, 4.1.2.2 and 4.1.2.3 provide details on how to connect the transmit payload data interface block with the terminal equipment when the back-plane interface data rate is 1.544mbit/s. when the back-plane interface data rate is mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s, the transmit serial clock, transmit serial data, transmit single-frame synchronization signal and transmit multi-frame synchronization signal are all configured as inputs. the transmit serial clock is always an input clock with frequency of 1.544 mhz for all data rates. the txmsync_n signal is configured as the transmit input clock with frequencies of 2.048 mhz, 4.096 mhz and 8.192 mhz respectively. it serves as the primary clock source for the high-speed back-plane interface. the table below summaries the clock frequencies of txserclk_n and txinclk_n inputs when the framer is operating in non-multiplexed high-speed back-plane mode. when the transmit multiplex enable bit is set to one, the framer is configured in channel-multiplexed mode. the possible data rates are multiplexed 12.352mbit/s, bit-multiplexed 16.384mbit/s, hmvip 16.384mbit/s and h.100 16.384mbit/s. in channel-multiplexed mode, every four channels share the transmit serial data and transmit single-frame synchronization signal of one channel as interface between the framer and the local terminal equipment. the txmsync_n signal of one channel is configured as the transmit input clock with frequencies of 12.352 mhz or 16.384. it serves as the primary clock source for the high-speed back-plane interface. t able 38: t ransmit m ultiplex e nable bit and t ransmit i nterface m ode s elect [1:0] bits with the resulting t ransmit b ack - plane i nterface data rates t ransmit m ultiplex e nable b it t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate 0 0 0 1.544mbit/s 0 0 1 mvip 2.048mbit/s 0 1 0 4.096mbit/s 0 1 1 8.192mbit/s 1 0 0 multiplexed 12.352mbit/s 1 0 1 bit multiplexed 16.384mbit/s 1 1 0 hmvip 16.384mbit/s 1 1 1 h.100 16.384mbit/s transmit multiplex enable bit = 0 t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate t x s er c lk t x ms ync /t x i n c lk 0 0 1.544mbit/s 1.544 mhz - 0 1 mvip 2.048mbit/s 1.544 mhz 2.048 mhz 1 0 4.096mbit/s 1.544 mhz 4.096 mhz 1 1 8.192mbit/s 1.544 mhz 8.192 mhz
xrt84l38 193 rev. 1.0.1 octal t1/e1/j1 framer payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. the transmit single-frame synchronization signal of channel 0 pulses high at the beginning of the frame with data from channel 0-3 multiplexed together. the transmit single-frame synchronization signal of channel 4 pulses high at the beginning of the frame with data from channel 4-7 multiplexed together. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. additionally, each channel requires the local terminal equipment to provide a free-running 1.544 mhz clock into the transmit serial clock input. the table below summaries the clock frequencies of txserclk_n and txinclk_n inputs when the framer is operating in multiplexed high-speed back-plane mode. the transmit serial clock is always running at 1.544mhz for all the high-speed back-plane interface modes. it is automatically the timing source of the transmit section of the framer in high-speed back-plane interface mode. the transmit single-frame synchronization signal should pulse high or low for one bit period at the framing bit position of each ds1 frame. length of the bit period depends on data rate of the high-speed back-plane interface. the transmit synchronization pulse low bit of the transmit interface control register (ticr) determines whether the transmit single-frame synchronization signal is high active or low active. the table below shows configurations of the transmit synchronization pulse low bit of the transmit interface control register (ticr). throughout the discussion of this datasheet, we assume that the transmit single-frame synchronization signal pulses high unless stated otherwise. the txmsync_n signal, which is a multiplexed i/o pin, no longer functions as the transmit multi-frame synchronization signal. indeed, it becomes the transmit input clock signal (txinclk) of the high-speed back- plane interface of the framer. the local terminal equipment should provide a free-running clock with the same frequency as the high-speed back-plane interface to this input pin. the following sections discuss details of how to operate the framer in different back-plane interface speed mode and how to connect the transmit payload data input interface block to the local terminal equipment. transmit multiplex enable bit = 1 t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate t x s er c lk t x ms ync /t x i n c lk 0 0 multiplexed 12.352mbit/s 1.544 mhz 12.352 mhz 0 1 bit-multiplexed 16.384mbit/s 1.544 mhz 16.384 mhz 1 0 hmvip 16.384mbit/s 1.544 mhz 16.384 mhz 1 1 h.100 16.384mbit/s 1.544 mhz 16.384 mhz transmit interface control register (ticr) (indirect address = 0xn0h, 0 x20h) b it n umber b it n ame b it t ype b it d escription 3 transmit synchronization pulse low r/w 0 - the transmit single-frame synchronization signal will pulse high indicat - ing the beginning of a ds1 frame when the high-speed back-plane interface is running at a mode other than the 1.544mbit/s. 1 - the transmit single-frame synchronization signal will pulse low indicat - ing the beginning of a ds1 frame when the high-speed back-plane interface is running at a mode other than the 1.544mbit/s.
xrt84l38 194 octal t1/e1/j1 framer rev. 1.0.1 4.1.3.1 t1 transmit input interface - mvip 2.048 mhz when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 01, the transmit back-plane interface of framer is running at a data rate of 2.048mbit/s. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_n at an e1 equivalent data rate of 2.048mbit/ s. the local terminal equipment supplies a free-running 2.048mhz clock to the transmit input clock pin of the framer. the local terminal equipment also provides synchronized payload data at rising edge of the clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the transmit input clock. the local terminal equipment should pump in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the local terminal equipment maps a 193-bit t1 frame into this 256-bit format as described below: 1. the framing (f-bit) is mapped into msb of the first e1 time-slot. the local terminal equipment will stuff the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the local terminal equipment will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the framer. 4. following the same rules of step 2 and 3, the local terminal equipment maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning (f-bit position) of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single- frame synchronization signal, the framer can position the beginning of a ds1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are then processed by the framer and send to liu interface. the local terminal equipment provides a free-running t able 39: t he mapping of t1 frame into e1 framing format t1 f-bit ts0 ts1 ts2 don't care bits ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 195 rev. 1.0.1 octal t1/e1/j1 framer 1.544mhz clock to the transmit serial input clock. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. see figure 29 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in mvip 2.048mbit/s mode. the timing diagram of input signals to the framer when running at mvip 2.048mbit/s mode is shown in figure 30 . 4.1.3.2 t1 transmit input interface - 4.096 mhz this interface mode is the same as running at 2.048 mhz. the only difference is that the transmit input clock runs two times faster at 4.096 mhz. f igure 29. i nterfacing xrt84l38 to the local t erminal e quipment using mvip 2.048m bit / s d ata b us f igure 30. t iming d iagram of the i nput s ignals to the f ramer when running at mvip 2.048m bit / s m ode txserclk_0 txser_0 txinclk_0 (2.048mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (2.048mhz) txsync_7 txserclk txserclk (inv) txser txsync(input) txsync(input) mvip mode txtsclk txtsb[0]/txsig txsyncfrd=0 txtsb[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care don't care c a b d don't care don't care note: the following signals are not aligned with the signals shown above. the txtsclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txtsb[1]/txfrtd txtsclk txsyncfrd=1
xrt84l38 196 octal t1/e1/j1 framer rev. 1.0.1 when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 10, the transmit back-plane interface of framer is running at a clock rate of 4.096mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is still accepting data through txser_n at an e1 equivalent data rate of 2.048mbit/s. however, the local terminal equipment supplies a free-running 4.096mhz clock to the transmit input clock pin of the framer. the local terminal equipment provides synchronized payload data at every other rising edge of the transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at every other falling edge of the clock. the local terminal equipment should pump in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the local terminal equipment maps a 193-bit t1 frame into this 256-bit format as described below: 1. the framing (f-bit) is mapped into msb of the first e1 time-slot. the local terminal equipment will stuff the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the local terminal equipment will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the framer. 4. following the same rules of step 2 and 3, the local terminal equipment maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning (f-bit position) of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single- frame synchronization signal, the framer can position the beginning of a ds1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are then processed by the framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. t able 40: t he mapping of t1 frame into e1 framing format t1 f-b it ts0 ts1 ts2 d on ' t c are b its ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 197 rev. 1.0.1 octal t1/e1/j1 framer see figure 31 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in mvip 4.096mbit/s mode. the timing diagram of input signals to the framer when running at 4.096mbit/s mode is shown in figure 32 4.1.3.3 t1 transmit input interface - 8.192 mhz this interface mode is the same as running at 2.048 mhz. the only difference is that the transmit input clock runs four times faster at 8.192mhz. when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 11, the transmit back-plane interface of framer is running at a clock rate of 8.192mhz. the interface consists of the following pins: f igure 31. i nterfacing xrt84l38 to the local t erminal e quipment using 4.096m bit / s d ata b us f igure 32. t iming d iagram of the i nput s ignals to the f ramer when running at 4.096m bit / s m ode txserclk_0 txser_0 txinclk_0 (4.096mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (4.096mhz) txsync_7 txserclk (2mhz) txserclk (inv) txser txsync(input) txtsclk(inv) txtsb[0]/txsig txtsb[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txtsclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txserclk (4mhz) don't care don't care
xrt84l38 198 octal t1/e1/j1 framer rev. 1.0.1 ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is still accepting data through txser_n at an e1 equivalent data rate of 2.048mbit/s. however, the local terminal equipment supplies a free-running 8.192mhz clock to the transmit input clock pin of the framer. the local terminal equipment provides synchronized payload data at every other four rising edge of the transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at every other four falling edge of the clock. the local terminal equipment should pump in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the local terminal equipment maps a 193-bit t1 frame into this 256-bit format as described below: 1. the framing (f-bit) is mapped into msb of the first e1 time-slot. the local terminal equipment will stuff the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the local terminal equipment will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the framer. 4. following the same rules of step 2 and 3, the local terminal equipment maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning (f-bit position) of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single- frame synchronization signal, the framer can position the beginning of a ds1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are then processed by the framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. t able 41: t he mapping of t1 frame into e1 framing format t1 f-bit ts0 ts1 ts2 don't care bits ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 199 rev. 1.0.1 octal t1/e1/j1 framer see figure 33 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in mvip 8.192mbit/s mode. the timing diagram of input signals to the framer when running at 8.192mbit/s mode is shown in figure 34 . 4.1.3.4 t1 transmit input interface - multiplexed 12.352mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 00, the transmit back-plane interface of framer is running at a clock rate of 12.352mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) f igure 33. i nterfacing xrt84l38 to the l ocal t erminal e quipment using 8.192m bit / s d ata b us f igure 34. t iming d iagram of the i nput s ignals to the f ramer when running at 8.192m bit / s m ode txserclk_0 txser_0 txinclk_0 (8.192mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (8.192mhz) txsync_7 txserclk (2mhz) txserclk (inv) txser txsync(input) txtsclk(inv) txtsb[0]/txsig txtsb[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txtsclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txserclk (8mhz) don't care don't care
xrt84l38 200 octal t1/e1/j1 framer rev. 1.0.1 ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 12.352mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 12.352mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 1.544mbit/s ds1 data streams into this 12.352mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f x : f-bit of channel x 2. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demon - strates how payload bits of four channels are mapped into the 12.352mbit/s data stream. x y : the xth payload bit of channel y 3. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 12.352mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a first octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 second octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 third octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3
xrt84l38 201 rev. 1.0.1 octal t1/e1/j1 framer particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. simi - larly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the sev - enth payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 12.352mbit/ s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 4. following the same rules of step 2 and 3, the local terminal equipment maps the payload data and signal - ing data of four channels into a 12.352mbit/s data stream. the transmit single-frame synchronization signal of channel 0 pulses high for one clock cycle at the first bit position (f-bit of channel 0) of the data stream with data from channel 0-3 multiplexed together. the transmit single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position (f-bit of channel 4) of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed ds1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. sixth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 seventh octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 eighth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3 nineth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 202 octal t1/e1/j1 framer rev. 1.0.1 see figure 35 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in 12.352mbit/s mode. the input signal timing is shown in figure 36 below when the framer is running at 12.352mbit/s mode. 4.1.3.5 t1 transmit input interface - bit-multiplexed 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 01, the transmit back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) f igure 35. i nterfacing xrt84l38 to the l ocal t erminal e quipment using b it -m ultiplexed 12.352m bit / s d ata b us f igure 36. t iming d iagram of the i nput s ignals to the f ramer when running at 12.352m bit / s m ode txser_0 txinclk_0 (12.352mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (12.352mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (12.352mhz) txserclk (inv) txser txsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3
xrt84l38 203 rev. 1.0.1 octal t1/e1/j1 framer ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f x : f-bit of channel x 2. after the first octet of data is sent, the local terminal equipment should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demon - strates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 nineth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3
xrt84l38 204 octal t1/e1/j1 framer rev. 1.0.1 4. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. simi - larly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the sev - enth payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/ s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the terminal equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, the local terminal equipment stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/s data stream is thus created. the transmit single-frame synchronization signal of channel 0 pulses high for one clock cycle at the first bit position (f-bit of channel 0) of the data stream with data from channel 0-3 multiplexed together. the transmit single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position (f-bit of channel 4) of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed ds1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3 sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 205 rev. 1.0.1 octal t1/e1/j1 framer inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. see figure 37 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in bit-multiplexed 16.384mbit/s mode. the input signal timing is shown in figure 38 below when the framer is running at bit-multiplexed 16.384mbit/s mode. 4.1.3.6 t1 transmit input interface - hmvip 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 10, the transmit back-plane interface of framer is running at a clock rate of 16.384mhz. f igure 37. i nterfacing xrt84l38 to the l ocal t erminal e quipment using 16.384m bit / s d ata b us f igure 38. t iming d iagram of the i nput s ignals to the f ramer when running at b it -m ultiplexed 16.384m bit / s m ode txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (16.384mhz) txserclk (inv) txser txsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 56 cycles
xrt84l38 206 octal t1/e1/j1 framer rev. 1.0.1 the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f x : f-bit of channel x 2. after the first octet of data is sent, the local terminal equipment should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equipment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 ninth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0
xrt84l38 207 rev. 1.0.1 octal t1/e1/j1 framer x y : the xth payload bit of channel y 4. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. simi - larly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the sev - enth payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. eleventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3 tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 twelfth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2
xrt84l38 208 octal t1/e1/j1 framer rev. 1.0.1 x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the terminal equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, the local terminal equipment stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/s data stream is thus created. the transmit single-frame synchronization signal should pulse high for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the transmit single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the transmit single-frame synchronization signal of channel 4 pulses high to identify the start of multiplexed data stream of channel 4-7. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed ds1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 209 rev. 1.0.1 octal t1/e1/j1 framer see figure 39 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in hmvip 16.384mbit/s mode. the input signal timing is shown in figure 40 below when the framer is running at hmvip 16.384mbit/s mode. 4.1.3.7 t1 transmit input interface - h.100 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 11, the transmit back-plane interface of framer is running at h.100 16.384mbit/s mode. (the hmvip mode and the h.100 mode are essential the same except for the high pulse position of the transmit single-frame synchronization signal) f igure 39. i nterfacing xrt84l38 to the l ocal t erminal e quipment using hmvip 16.384m bit / s d ata b us f igure 40. t iming d iagram of the i nput s ignals to the f ramer when running at hmvip 16.384m bit / s m ode txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (16.384mhz) txserclk (inv) txser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 txsig txsync(input) hmvip, negative sync txsync(input) hmvip, positive sync start of frame x y : x is the bit number and y is the channel number
xrt84l38 210 octal t1/e1/j1 framer rev. 1.0.1 the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. fx: f-bit of channel x 2. after the first octet of data is sent, the local terminal equipment should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. 3.payload data of four channels are repeated and grouped together in a byte-interleaved way. the first payload bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equip - ment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 ninth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0
xrt84l38 211 rev. 1.0.1 octal t1/e1/j1 framer x y : the xth payload bit of channel y 4. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. simi - larly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the sev - enth payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. eleventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3 tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 twelfth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2
xrt84l38 212 octal t1/e1/j1 framer rev. 1.0.1 x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the terminal equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, the local terminal equipment stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/s data stream is thus created. the transmit single-frame synchronization signal should pulse high for two clock cycles (the last bit position of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the transmit single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the transmit single-frame synchronization signal of channel 4 pulses high to identify the start of multiplexed data stream of channel 4-7. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed ds1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 213 rev. 1.0.1 octal t1/e1/j1 framer see figure 41 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in h.100 16.384mbit/s mode. the input signal timing is shown in figure 42 below when the framer is running at h.100 16.384mbit/s mode. f igure 41. i nterfacing xrt84l38 to the l ocal t erminal e quipment using h.100 16.384m bit / s d ata b us f igure 42. t iming d iagram of the i nput s ignals to the f ramer when running at h.100 16.384m bit / s m ode txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (16.384mhz) txserclk (inv) txser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 txsig start of frame x y : x is the bit number and y is the channel number txsync(input) h.100, negative sync txsync(input) h.100, positive sync delayer h.100 txsync(input) h.100, negative sync txsync(input) h.100, positive sync
xrt84l38 214 octal t1/e1/j1 framer rev. 1.0.1 5.0 the ds1 receive section 5.1 the ds1 receive payload data output interface block 5.1.1 description of the receive payload data output interface block each of the eight framers within the xrt84l38 includes a receive payload data output interface block. the function of the block is to provide an interface to the terminal equipment (for example, a central office or switching equipment) that has data to receive from a "far end" terminal over a ds1 or e1 transport medium. the payload data output interface module (also known as the back-plane interface module) supports payload data to be taken from or presented to the system. in ds1 mode, supported data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. in e1 mode, supported data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the receive payload data output interface block supplies or accepts the following signals to the terminal equipment circuitry: ? receive serial data input (rxser_n) ? receive serial clock (rxserclk_n) ? receive single-frame synchronization signal (rxsync_n) ? receive multi-frame synchronization signal (rxmsync_n) ? receive time-slot indicator clock (rxtsclk_n) ? receive time-slot indication bits (rxtsb[4:0]_n) the receive serial data is an output pin carrying payload, signaling and sometimes data link data supplied by xrt84l38 to the local terminal equipment. the receive serial clock is an input or output signal used by the receive payload data input interface block to send out serial data to the local terminal equipment. the receive clock inversion bit of the receive interface control register (ticr) determines at which edge of the receive serial clock would data transition on the receive serial data pin occur. the table below shows configurations of the receive clock inversion bit of the receive interface control register (ricr). throughout the discussion of this datasheet, we assume that serial data transition happens on the rising edge of the receive serial clock unless stated otherwise. the receive single-frame synchronization signal is either input or output. when configured as input, it indicates beginning of a ds1 frame. when configured as output, it indicates the end of a ds1 frame. the receive multi-frame synchronization signal is an output pin from xrt84l38 indicating the end of a ds1 multi-frame. by connecting these signals with the local terminal equipment, the receive payload data output interface routes received payload data from the receive framer module to the local terminal equipment. 5.1.2 the receive payload data output interface block operating at 1.544mbit/s mode receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 3 receive clock inversion r/w 0 - serial data transition happens on rising edge of the receive serial clock. 1 - serial data transition happens on falling edge of the receive serial clock.
xrt84l38 215 rev. 1.0.1 octal t1/e1/j1 framer the incoming receive payload data is taken into the framer from the liu interface using the recovered receive line clock. the payload data is then routed through the receive farmer module and presented to the receive payload data output interface through the receive serial data output pin (rxser_n). this data is then clocked out using the receive serial clock (rxserclk_n). there is a two-frame (512 bits) elastic buffer between the receive framer module and the receive payload data output interface. this buffer can be enabled or disabled via programming the slip buffer enable [1:0] bits in slip buffer control register (sbcr). the following table shows configurations of the slip buffer enable [1:0] bits in slip buffer control register. if the slip buffer is not in bypass mode, then the user has the option of either providing the receive single- frame synchronization pulse or getting the receive single-frame synchronization pulse on frame boundary at the rxsync_n pin. the slip buffer receive synchronization direction bit of the slip buffer control register (sbcr) determines whether the receive single-frame synchronization signal is input or output. the table below demonstrates settings of the slip buffer receive synchronization direction bit of the slip buffer control register. if the slip buffer is in bypass mode, the receive payload data is routed to the receive payload data output interface from the receive framer module directly. the recovered line clock is used to carry the receive payload data all the way from the liu interface, to the receive framer module and eventually output through the receive serial data output pin. the receive serial clock signal is therefore an output using the recovered receive line clock as timing source. the receive single-frame synchronization signal is also output in slip buffer bypass mode. if the slip buffer is enabled, the receive payload data is latched into the elastic store using the recovered receive line clock. the local terminal equipment supplies a free-running 1.544mhz clock to the receive serial clock pin to latch the receive payload data out from the elastic store. since the recovered receive slip buffer control register (sbcr) (indirect address = 0xn0h, 0x16h) b it n umber b it n ame b it t ype b it d escription 1-0 slip buffer enable r/w 00 - slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output. 01 - the elastic store (slip buffer) is enabled. the receive payload data is passing from the receive framer module through the slip buffer to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. 10 - the slip buffer acts as a fifo. the fifo latency register (flr) deter - mines the data latency. the receive payload data is passing from the receive framer module through the fifo to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. 11 - slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output. slip buffer control register (sbcr) (indirect address = 0xn0h, 0x16h) b it n umber b it n ame b it t ype b it d escription 2 slip buffer receive synchronization direction r/w 0 - the receive single-frame synchronization signal (rxsync_n) is an output if the slip buffer is not in bypass mode. 1 - the receive single-frame synchronization signal (rxsync_n) is an input if the slip buffer is not in bypass mode.
xrt84l38 216 octal t1/e1/j1 framer rev. 1.0.1 line clock and the receive serial clock are coming from different timing sources, the slip buffer will gradually fill or empty. if the elastic buffer either fills or empties, a controlled slip will occur. if the buffer empties and a read occurs, then a full frame of data will be repeated and a status bit will be updated. if the buffer fills and a write comes, then a full frame of data will be deleted and another status bit will be set. a detailed description of the elastic buffer can be found in later sections. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. if the slip buffer is put into a fifo mode, it is acting like a standard first-in-first-out storage. a fixed read and write latency is maintained in a programmable fashion controlled by the fifo latency register (fifolr). the local terminal equipment supplies a 1.544mhz clock to the receive serial clock pin to latch the receive payload data out from the fifo. however, it is the responsibility of the user to phase lock the input receive serial clock to the recovered receive line clock to avoid either over-run or under-run of the fifo. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. the following table summaries the input or output nature of the receive serial clock and receive single- frame synchronization signals for different slip buffer settings. t able 42: t he r eceive s erial c lock and r eceive s ingle -f rame s ynchronization signals for different s lip b uffer settings r eceive t iming s ource r x s er c lk _ n r x s ync _ n s lip b uffer s ynchronization d irection b it = 0 s lip b uffer s ynchronization d irection b it = 1 slip buffer bypassed output output output slip buffer enabled input output input slip buffer acts as fifo input output input
xrt84l38 217 rev. 1.0.1 octal t1/e1/j1 framer the receive time-slot indication bits (rxtsb[4:0]_n) are multiplexed i/o pins. the functionality of these pins is governed by the value of receive fractional t1 output enable bit of the receive interface control register (ricr). the following table illustrates the configurations of the receive fractional ds1 input enable bit. when configured to operate in normal condition (that is, when the receive fractional t1 input enable bit is equal to zero), these bits reflect the five-bit binary value of the time slot number (0 - 23) being outputted and processed by the receive payload data output interface block of the framer. rxtsb[4] represents the msb of the binary value and rxtsb[0] represents the lsb. when the receive fractional t1 output enable bit is equal to one, the rxtsb[0]_n bit becomes the receive fractional t1 output signal (rxfrtd_n). this output pin carries fractional t1 output data extracted by the framer from the incoming ds1 data stream. the fractional t1 output interface allows certain time-slots of ds1 data to be routed to destinations other than the local terminal equipment. function of the fractional t1 output signal will be discussed in details in later sections. when the receive fractional t1 output enable bit is equal to one, the rxtsb[1]_n bit becomes the receive signaling data output signal (rxsig_n). these output pins can be used to carry robbed-bit signaling data extracted from the inbound ds1 frame. function of the receive signaling data output signal will be discussed in details in later sections. when the receive fractional t1 output enable bit is equal to one, the rxtsb[2]_n bit serially outputs all five- bit binary values of the time slot number (0-23) being outputted and processed by the receive payload data output interface block of the framer. msb of the binary value is presented first and the lsb is presented last. the rxtsb[3]_n and rxtsb[4}_n pins are not multiplexed. receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 4 receive fractional ds1 output enable r/w 0 - the receive time-slot indication bits (rxtsb[4:0] are outputting five-bit binary values of time-slot number (0-23) being accepted and processed by the receive payload data output interface block of the framer. the receive time-slot indicator clock signal (rxtsclk_n) is a 192khz clock that pulses high for one ds1 bit period whenever the receive payload data output interface block is accepting the lsb of each of the twenty-four time slots. 1 - the rxtsb[0]_n bit becomes the receive fractional t1 output signal (rxfrtd_n) which carries fractional ds1 payload data from the framer. the rxtsb[1]_n bit becomes the receive signaling data output signal (rxsig_n) which is used to carry robbed-bit signaling data extracted from the inbound ds1 frame. the rxtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-23) being accepted and processed by the receive payload data out - put interface block of the framer. the rxtsclk_n will output gaped fractional ds1 clock that can be used by ter - minal equipment to latch in fractional ds1 payload data at rising edge of the clock. or, the rxtsclk_n pin will be a clock enable signal to receive fractional ds1 out - put signal (rxfrtd_n) when the un-gaped receive serial output clock (rxserclk_n) is used to latch in fractional ds1 payload data into the terminal equipment.
xrt84l38 218 octal t1/e1/j1 framer rev. 1.0.1 the table below shows functionality of the rxtsb[2:0] bits when the receive fractional t1 output bit is set to different values. the receive time-slot indicator clock signal (rxtsclk_n) is a multi-function output pin. when configured to operate in normal condition (that is, when the receive fractional t1 input enable bit is equal to zero), the rxtsclk_n is a 192khz clock that pulses high for one ds1 bit period whenever the receive payload data output interface block is outputting the lsb of each of the twenty-four time slots. the local terminal equipment should use this clock signal to sample the rxtsb[0] through rxtsb[4] bits and identify the time-slot being processed via the receive section of the framer. when the receive fractional t1 output enable bit is equal to one, the rxtsclk_n will output gaped fractional ds1 clock whenever fractional ds1 payload data is present at the rxfrtd_n pin. the local terminal equipment can latch in fractional ds1 payload data at falling edge of the clock. otherwise, this pin will be a clock enable signal to receive fractional ds1 output signal (rxfrtd_n) if the framer is configured accordingly. in this way, fractional ds1 payload data is clocked into the terminal equipment using un-gaped receive serial output clock (rxserclk_n). a detailed discussion of the fractional ds1 payload data output interface can be found in later sections. a detailed discussion of how to connect the receive payload data output interface block to the local terminal equipment with slip buffer enabled or disabled can be found in the later sections. 5.1.2.1 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is bypassed by setting the slip buffer enable [1:0] bits of the slip buffer control register to 00 or 11, the receive framer module routes the receive payload data directly to the receive payload data output interface without passing through the elastic buffer. the xrt84l38 uses the recovered receive line clock internally to carry the receive payload data directly across the whole chip. the recovered receive line clock is essentially become timing source of the receive serial clock output. if the slip buffer is bypassed, the receive single-frame synchronization signal is automatically configured to be output signals. it should pulse high for one ds1 bit period (648ns) at the last bit position of each ds1 frame. by triggering on the high pulse on the receive single-frame synchronization signal, the terminal equipment can identify the end of a ds1 frame and should prepare to accept payload data of the next ds1 frame from the framer. the receive multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of a ds1 multi-frame. by triggering on the high pulse on the receive multi-frame synchronization signal, the framer can identify the end of a ds1 super-frame and should prepare to accept payload data of the next ds1 super-frame from the framer. t able 43: t he r x ts b [2:0] bits when the r eceive f ractional t1 o utput bit is set to different values r eceive f ractional t1 o utput b it = 0 r eceive f ractional t1 o utput b it = 1 rxtsb[0] output rxfrtd output rxtsb[1] output rxsig output rxtsb[2] output rxts output
xrt84l38 219 rev. 1.0.1 octal t1/e1/j1 framer see figure 43 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is bypassed and the recovered receive line clock is timing source of the receive section. the following figure 44 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal f igure 43. i nterfacing xrt84l38 local t erminal e quipment with s lip b uffer b ypassed and r ecov - ered r eceive l ine c lock as r eceive t iming s ource rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxlineclk_0 rxlineclk_7
xrt84l38 220 octal t1/e1/j1 framer rev. 1.0.1 equipment when the slip buffer is bypassed and the recovered receive line clock is timing source of the receive section. 5.1.2.2 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is enabled by setting the slip buffer enable [1:0] bits of the slip buffer control register to 01, the framer includes the two- frame elastic buffer into its data path. the receive framer module routes the receive payload data to the elastic buffer first. the receive payload data is then presented to the receive payload data output interface. the xrt84l38 uses the recovered receive line clock internally to clock in the receive payload data into the elastic buffer. the terminal equipment should provide a 1.544mhz clock to the receive serial clock input pin to latch data out from the elastic buffer. the recovered receive line clock and the receive serial clock are generated from two different timing sources. that is, the recovered receive line clock is originating from a remote site while receive serial clock generating by a local oscillator. any mismatch in frequencies of these two clocks will result in the slip buffer to gradually fill or deplete. overtime, the elastic buffer either fills or empties completely. once that happened, a controlled slip by the xrt84l38 will occur. the receive slip buffer slip bit of the slip buffer status register (sbsr) is set to 1. if the buffer empties and a read occurs, then a full frame of data will be repeated and the receive slip buffer empty bit of the slip buffer status register (sbsr) will be forced high. if the buffer fills and a write comes, then a full frame of data will be deleted and the receive slip buffer full bit of the slip buffer status register (sbsr) will be forced high. the following table demonstrates settings of the receive slip buffer slip bit, receive slip buffer empty bit and receive slip buffer full bit of the slip buffer status register. f igure 44. w aveforms of the s ignals c onnecting the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is b ypassed and the r ecovered l ine c lock is the t iming s ource of the r eceive s ection c rxserclk rxser rxsync(input) rxsync(output) rxtsclk rxtsb[4:0] rxtsb[0]/rxsig rxtsclk rxtsb[2]/rxtsb rxtsb[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 221 rev. 1.0.1 octal t1/e1/j1 framer in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. when the slip buffer receive synchronization direction bit is set to 0, the receive single-frame synchronization signal (rxsync_n) is an output. when the slip buffer receive synchronization direction bit is set to 1,the receive single-frame synchronization signal (rxsync_n) is an input. if the receive single-frame synchronization signal is an output, it should pulse high for one ds1 bit period (648ns) at the last bit position of each ds1 frame. by triggering on the high pulse on the receive single- frame synchronization signal, the terminal equipment can identify the end of a ds1 frame and should prepare to accept payload data of the next ds1 frame from the framer. if the receive single-frame synchronization signal is an input, it should pulse high for one ds1 bit period (648ns) at the first bit position (f-bit) of each ds1 frame. by sampling the high pulse of the receive single- frame synchronization signal, the framer should identify the beginning of a ds1 frame and can send out data in a synchronized way. it is the responsibility of the local terminal equipment to align the start of a ds1 frame with the receive single-frame synchronization pulse. the receive multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of frame number one of a ds1 multi-frame. by triggering on the high pulse on the receive multi- frame synchronization signal, the framer can identify the end of a ds1 super-frame and should prepare to accept payload data of the next ds1 super-frame from the framer. slip buffer status register (sbs r) (indirect address = 0xnah, 0x08h) b it n umber b it n ame b it t ype b it d escription 2 receive slip buffer full r/w 0 - the receive slip buffer is not full. 1 - the receive slip buffer is full and one frame of data is discarded. 1 receive slip buffer empty r/w 0 - the receive slip buffer is not empty. 1 - the receive slip buffer is empty and one frame of data is repeated. 0 receive slip buffer slip r/w 0 - the receive slip buffer does not slip. 1 - the receive slip buffer slips since either full or emptied.
xrt84l38 222 octal t1/e1/j1 framer rev. 1.0.1 see figure 45 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is enabled. f igure 45. i nterfacing xrt84l38 to local t erminal e quipment with s lip b uffer e nabled or a cts as fifo rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 223 rev. 1.0.1 octal t1/e1/j1 framer the following figure 46 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal equipment when the slip buffer is enabled. 5.1.2.3 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is configured as fifo by setting the slip buffer enable [1:0] bits of the slip buffer control register to 10, the framer puts the elastic buffer into fifo mode. receive framer module routes the receive payload data through the first-in-first-out storage to the receive payload data output interface. the xrt84l38 uses the recovered receive line clock internally to clock in the receive payload data into the fifo. the terminal equipment should provide an external 1.544mhz clock to the receive serial clock input pin to latch data out from the fifo. it is the responsibility of the user to phase lock the input receive serial clock to the recovered receive line clock to avoid either over-run or under-run of the fifo. the latency between writing a bit into the fifo and reading the same bit from it (read and write latency) is actually depth of the fifo, which is maintained in a programmable fashion controlled by the fifo latency register (fifolr). the largest possible depth of the fifo is thirty-two bytes or one e1 frame. the default depth of the fifo when xrt84l38 first powered up is four bytes. the table below shows the fifo latency register. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. when the slip buffer receive synchronization direction bit is set to 0, the receive single-frame synchronization signal f igure 46. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is e nabled fifo latency register (fifolr) (indirect address = 0xn0h, 0x17h) b it n umber b it n ame b it t ype b it d escription 4-0 fifo latency r/w these bits determine depth of the fifo in terms of bytes. the largest possible value is thirty-two bytes or one e1 frame. c rxserclk rxser rxsync(input) rxsync(output) rxtsclk rxtsb[4:0] rxtsb[0]/rxsig rxtsclk rxtsb[2]/rxtsb rxtsb[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 224 octal t1/e1/j1 framer rev. 1.0.1 (rxsync_n) is an. when the slip buffer receive synchronization direction bit is set to 1,the receive single- frame synchronization signal (rxsync_n) is an input. if the receive single-frame synchronization signal is an output, it should pulse high for one ds1 bit period (648ns) at the last bit position of each ds1 frame. by triggering on the high pulse on the receive single- frame synchronization signal, the terminal equipment can identify the end of a ds1 frame and should prepare to accept payload data of the next ds1 frame from the framer. if the receive single-frame synchronization signal is an input, it should pulse high for one ds1 bit period (648ns) at the first bit position (f-bit) of each ds1 frame. by sampling the high pulse of the receive single- frame synchronization signal, the framer should identity the beginning of a ds1 frame and can send out data in a synchronized way. it is the responsibility of the local terminal equipment to align the start of a ds1 frame with the receive single-frame synchronization pulse. the receive multi-frame synchronization signal should pulse high for one ds1 bit period (648ns) at the last bit position of frame number one of a ds1 multi-frame. by triggering on the high pulse on the receive multi- frame synchronization signal, the framer can identify the end of a ds1 super-frame and should prepare to accept payload data of the next ds1 super-frame from the framer. see figure 47 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is acted as fifo. the following figure 48 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal equipment when the slip buffer is acted as fifo. f igure 47. i nterfacing xrt84l38 to local t erminal e quipment with s lip b uffer e nabled or a cts as fifo rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 225 rev. 1.0.1 octal t1/e1/j1 framer 5.1.3 high speed receive back-plane interface the high-speed back-plane interface supports payload data to be taken from or presented to the local terminal equipment at a rate higher than 1.544mbit/s. in ds1 mode, supported high-speed data rates are mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the receive multiplex enable bit and the receive interface mode select [1:0] bits of the receive interface control register (ricr) determine the receive back-plane interface data rate. the following table shows configurations of the receive multiplex enable bit and the receive interface mode select [1:0] bits of the receive interface control register (ricr). f igure 48. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is acted as fifo receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 2 receive multiplex enable r/w 0 - the receive back-plane interface block is configured to non-channel-multi - plexed mode. 1 - the receive back-plane interface block is configured to channel-multiplexed mode 1-0 receive interface mode select r/w when combined with the receive multiplex enable bit, these bits determine the receive back-plane interface data rate. c rxserclk rxser rxsync(input) rxsync(output) rxtsclk rxtsb[4:0] rxtsb[0]/rxsig rxtsclk rxtsb[2]/rxtsb rxtsb[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 226 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the combinations of receive multiplex enable bit and receive interface mode select [1:0] bits and the resulting receive back-plane interface data rates. when the receive multiplex enable bit is set to zero, the framer is configured in non-channel-multiplexed mode. the possible data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s. in non- channel-multiplexed mode, payload data of each channel are sending out from the receive high-speed back- plane interface separately. each channel uses its own receive serial clock, receive serial data, receive single-frame synchronization signal and receive multi-frame synchronization signal as interface between the framer and the terminal equipment. section 5.1.1.1, 5.1.1.2 and 5.1.1.3 provide details on how to connect the receive payload data interface block with the local terminal equipment when the back-plane interface data rate is 1.544mbit/s. when the back-plane interface data rate is mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s, the receive serial clock, receive serial data and receive single-frame synchronization are all configured as inputs. the receive multi-frame synchronization signal is still output. the receive serial clock is configured as an input timing source for the high-speed back-plane interface with frequencies of 2.048 mhz, 4.096 mhz and 8.192 mhz respectively. the table below summaries the clock frequencies of rxserclk_n input when the framer is operating in non- multiplexed high-speed back-plane mode. when the receive multiplex enable bit is set to one, the framer is configured in channel-multiplexed mode. the possible data rates are multiplexed 12.352mbit/s, bit-multiplexed 16.384mbit/s, hmvip 16.384mbit/s and h.100 16.384mbit/s. in channel-multiplexed mode, four channels share the receive serial data, receive single-frame synchronization signal and receive serial clock of one channel as interface between the framer and the terminal equipment. the receive serial clock runs at frequencies of 12.352 mhz or 16.384 mhz. it serves as the primary clock source for the high-speed back-plane interface. t able 44: r eceive m ultiplex e nable bit and r eceive i nterface m ode s elect [1:0] bits with the resulting r eceive b ack - plane i nterface data rates r eceive m ultiplex e nable b it r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate 0 0 0 1.544mbit/s 0 0 1 mvip 2.048mbit/s 0 1 0 4.096mbit/s 0 1 1 8.192mbit/s 1 0 0 multiplexed 12.352mbit/s 1 0 1 bit multiplexed 16.384mbit/s 1 1 0 hmvip 16.384mbit/s 1 1 1 h.100 16.384mbit/s receive multiplex enable bit = 0 r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate r x s er c lk 0 0 1.544mbit/s 1.544mhz 0 1 mvip 2.048mbit/s 2.048 mhz 1 0 4.096mbit/s 4.096 mhz 1 1 8.192mbit/s 8.192 mhz
xrt84l38 227 rev. 1.0.1 octal t1/e1/j1 framer payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. the receive single-frame synchronization signal of channel 0 pulses high at the beginning of the frame with data from channel 0-3 multiplexed together. the receive single-frame synchronization signal of channel 4 pulses high at the beginning of the frame with data from channel 4-7 multiplexed together. the table below summaries the clock frequencies of rxserclk_n input when the framer is operating in multiplexed high-speed back-plane mode. when the frame is running at high-speed back-plane interface mode other than the 1.544mbit/s data rate, the receive single-frame synchronization signal could pulse high or low indicating boundaries of ds1 frames. the receive synchronization pulse low bit of the receive interface control register (ticr) determines whether the receive single-frame synchronization signal is high active or low active. the table below shows configurations of the receive synchronization pulse low bit of the receive interface control register (ricr). throughout the discussion of this datasheet, we assume that the receive single-frame synchronization signal pulses high unless stated otherwise. the following sections discuss details of how to operate the framer in different back-plane interface speed mode and how to connect the receive payload data output interface block to the local terminal equipment. 5.1.3.1 t1 receive input interface - mvip 2.048 mhz when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 01, the receive back-plane interface of framer is running at a data rate of 2.048mbit/s. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) receive multiplex enable bit = 1 r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate r x s er c lk 0 0 multiplexed 12.352mbit/s 12.352 mhz 0 1 bit-multiplexed 16.384mbit/s 16.384 mhz 1 0 hmvip 16.384mbit/s 16.384 mhz 1 1 h.100 16.384mbit/s 16.384 mhz receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 3 receive synchronization pulse low r/w 0 - the receive single-frame synchronization signal will pulse high indicat - ing the beginning of a ds1 frame when the high-speed back-plane interface is running at a mode other than the 1.544mbit/s. 1 - the receive single-frame synchronization signal will pulse low indicat - ing the beginning of a ds1 frame when the high-speed back-plane interface is running at a mode other than the 1.544mbit/s.
xrt84l38 228 octal t1/e1/j1 framer rev. 1.0.1 ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 2.048mhz clock to the receive serial clock input. the receive high-speed back-plane interface of the framer then sends out serial data at rising edge of the receive serial clock. the local terminal equipment samples the serial data at falling edge of the clock. the terminal equipment take in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the receive high-speed back-plane interface maps a 193-bit t1 frame into this 256-bit format as described below: 1. the f-bit is mapped into msb of the first e1 time-slot. the framer will insert seven "don't care" bits to the rest of the first octet that would be ignored by the local terminal equipment. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the receive high-speed back-plane interface will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the local terminal equipment. 4. following the same rules of step 2 and 3, the receive high-speed back-plane interface maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of a ds1 frame and start pumping payload data out. t able 45: t he mapping of t1 frame into e1 framing format t1 f-bit ts0 ts1 ts2 don't care bits ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 229 rev. 1.0.1 octal t1/e1/j1 framer see figure 49 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in mvip 2.048mbit/s mode. the timing diagram of input signals to the framer when running at mvip 2.048mbit/s mode is shown in figure 50 . 5.1.3.2 t1 receive input interface - 4.096 mhz this interface mode is the same as running at 2.048 mhz. the only difference is that the receive serial clock runs two times faster at 4.096 mhz. f igure 49. i nterfacing xrt84l38 to local t erminal e quipment using mvip 2.048m bit / s d ata b us f igure 50. t iming d iagram of i nput signals to the f ramer when running at mvip 2.048m bit / s [ rxserclk_0 (2.048mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (2.048mhz) rxser_7 rxmsync rxsync_7 rxserclk rxserclk(inv) rxser rxsync(input) rxsync(input) (mvip) rxtsb[0]/rxsig rxtsb[1]/frrxd rxtsclk (rxsyncfrtd=1) rxtsclk(inv) rxtsclk (rxsyncfrtd=1) timeslot 2 f timeslot 3 timeslot 4 timeslot 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d c a b d c a b d c a b d c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 rxtsb[2]/rxchn
xrt84l38 230 octal t1/e1/j1 framer rev. 1.0.1 when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 10, the receive back-plane interface of framer is running at a clock rate of 4.096mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 4.096mhz clock to the receive serial clock input. the receive high-speed back-plane interface of the framer then sends out serial data at every other rising edge of the receive serial clock. the local terminal equipment samples the serial data at every other falling edge of the clock. the terminal equipment take in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the receive high-speed back-plane interface maps a 193-bit t1 frame into this 256-bit format as described below: 1. the f-bit is mapped into msb of the first e1 time-slot. the framer will insert seven "don't care" bits to the rest of the first octet that would be ignored by the local terminal equipment. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the receive high-speed back-plane interface will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the local terminal equipment. 4. following the same rules of step 2 and 3, the receive high-speed back-plane interface maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of a ds1 frame and start pumping payload data out. t able 46: t he mapping of t1 frame into e1 framing format t1 f-bit ts0 ts1 ts2 don't care bits ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 231 rev. 1.0.1 octal t1/e1/j1 framer see figure 51 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in 4.096mbit/s mode. the timing diagram of input signals to the framer when running at 4.096mbit/s mode is shown in figure 52 . 5.1.3.3 t1 receive input interface - 8.192 mhz this interface mode is the same as running at 2.048 mhz. the only difference is that the receive serial clock runs four times faster at 8.192mhz. when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 11, the receive back-plane interface of framer is running at a clock rate of 8.192mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) f igure 51. i nterfacing xrt84l38 to local t erminal e quipment using 4.096m bit / s d ata b us f igure 52. t iming d iagram of i nput signals to the f ramer when running at 4.096m bit / s rxserclk_0 (4.096mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (4.096mhz) rxser_7 rxmsync_7 rxsync_7 rxser rxsync(input) rxtsclk(inv) rxchn[0]/rxsig rxtsb[1]/rxfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the rxchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 don't care don't care don't care rxserclk (4mhz)
xrt84l38 232 octal t1/e1/j1 framer rev. 1.0.1 ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 8.192mhz clock to the receive serial clock input. the receive high-speed back-plane interface of the framer then sends out serial data at every other four rising edge of the receive serial clock. the local terminal equipment samples the serial data at every other four falling edge of the clock. the terminal equipment take in data grouped in 256-bit frame 8000 times every second. each frame consists of thirty-two octets as in e1. the receive high-speed back-plane interface maps a 193-bit t1 frame into this 256-bit format as described below: 1. the f-bit is mapped into msb of the first e1 time-slot. the framer will insert seven "don't care" bits to the rest of the first octet that would be ignored by the local terminal equipment. 2. payload data of t1 time-slot 0, 1 and 2 are mapped into e1 time-slot 1, 2 and 3. 3. the receive high-speed back-plane interface will stuff e1 time-slot 4 with eight "don't care" bits that would be ignored by the local terminal equipment. 4. following the same rules of step 2 and 3, the receive high-speed back-plane interface maps every three time-slots of t1 payload data into four e1 time-slots. the mapping of t1 frame into e1 framing format is shown in the table below. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of a ds1 frame and start pumping payload data out. t able 47: t he mapping of t1 frame into e1 framing format t1 f-bit ts0 ts1 ts2 don't care bits ts3 ts4 ts5 e1 ts0 ts1 ts2 ts3 ts4 ts5 ts6 ts7 t1 don't care bits ts6 ts7 ts8 don't care bits ts9 ts10 ts11 e1 ts8 ts9 ts10 ts11 ts12 ts13 ts14 ts15 t1 don't care bits ts12 ts13 ts14 don't care bits ts15 ts16 ts17 e1 ts16 ts17 ts18 ts19 ts20 ts21 ts22 ts23 t1 don't care bits ts18 ts19 ts20 don't care bits ts21 ts22 ts23 e1 ts24 ts25 ts26 ts27 ts28 ts29 ts30 ts31
xrt84l38 233 rev. 1.0.1 octal t1/e1/j1 framer see figure 53 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in 8.192mbit/s mode. the timing diagram of input signals to the framer when running at 8.192mbit/s mode is shown in figure 54 . 5.1.3.4 t1 receive input interface - multiplexed 12.352mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 00, the receive back-plane interface of framer is running at a clock rate of 12.352mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) f igure 53. i nterfacing xrt84l38 to local t erminal e quipment using 8.192m bit / s d ata b us f igure 54. t iming d iagram of i nput signals to the f ramer when running at 8.192m bit / s rxserclk_0 (8.192mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (8.192mhz) rxser_7 rxmsync_7 rxsync_7 rxser rxsync(input) rxtsclk(inv) rxtsb[0]/rxsig rxtsb[1]/rxfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the rxchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 rxserclk (8mhz) don't care don't care
xrt84l38 234 octal t1/e1/j1 framer rev. 1.0.1 ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping data through rxser_0 or rxser_4 pins at 12.352mbit/s. it multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 12.352mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface multiplexes four 1.544mbit/s ds1 data streams into this 12.352mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f x : f-bit of channel x 2. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demon - strates how payload bits of four channels are mapped into the 12.352mbit/s data stream. x y : the xth payload bit of channel y 3. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 12.352mbit/s data stream. when receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a first octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 second octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 third octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3
xrt84l38 235 rev. 1.0.1 octal t1/e1/j1 framer of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signal - ing bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 12.352mbit/ s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 4. following the same rules of step 2 and 3, the receive high-speed back-plane interface maps the payload data and signaling data of four channels into a 12.352mbit/s data stream. the receive single-frame synchronization signal of chann el 0 pulses high for one clock cycle at the first bit position (f-bit of channel 0) of the data stream with data from channel 0-3 multiplexed together. the receive single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position (f-bit of channel 4) of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. sixth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 seventh octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 eighth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3 nineth octet of 12.352mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 236 octal t1/e1/j1 framer rev. 1.0.1 see figure 55 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in 12.352mbit/s mode. the input signal timing is shown in figure 56 below when the framer is running at 12.352mbit/s mode. 5.1.3.5 t1 receive input interface - bit-multiplexed 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 01, the receive back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. it multiplexes payload and signaling data of every four channels into one data stream. payload and signaling f igure 55. i nterfacing xrt84l38 to local t erminal e quipment using 12.352m bit / s d ata b us f igure 56. t iming d iagram of i nput signals to the f ramer when running at 12.352m bit / s rxserclk_0 (12.352mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4-7 terminal equipment xrt84l38 rxserclk_4 (12.352mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (12.352mhz) rxserclk (inv) rxser rxsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3
xrt84l38 237 rev. 1.0.1 octal t1/e1/j1 framer data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f x : f-bit of channel x 2. after the first octet of data is sent, the receive high-speed back-plane interface should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demon - strates how payload bits of four channels are mapped into the 16.384mbit/s data stream. xy: the xth payload bit of channel y 4. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signal - ing bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 ninth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3
xrt84l38 238 octal t1/e1/j1 framer rev. 1.0.1 the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/ s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the receive high-speed back-plane interface should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, the receive high-speed back-plane interface stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/ s data stream is thus created. the receive single-frame synchronization signal of chann el 0 pulses high for one clock cycle at the first bit position (f-bit of channel 0) of the data stream with data from channel 0-3 multiplexed together. the receive single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position (f-bit of channel 4) of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3 sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 239 rev. 1.0.1 octal t1/e1/j1 framer see figure 57 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in bit-multiplexed 16.384mbit/s mode. the input signal timing is shown in figure 58 below when the framer is running at bit-multiplexed 16.384mbit/ s mode. 5.1.3.6 t1 receive input interface - hmvip 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 10, the receive back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) f igure 57. i nterfacing xrt84l38 to local t erminal e quipment using 16.384m bit / s d ata b us f igure 58. t iming d iagram of i nput signals to the f ramer when running at b it - multiplexed 16.384m bit / s rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4-7 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (16.384mhz) rxserclk (inv) rxser rxsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 56 cycles
xrt84l38 240 octal t1/e1/j1 framer rev. 1.0.1 the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. the receive high-speed back-plane interface multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. fx: f-bit of channel x 2. after the first octet of data is sent, the receive high-speed back-plane interface insert seven octets (fifty- six bits) of "don't care" data into the outgoing data stream. 3. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equipment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 ninth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 eleventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1
xrt84l38 241 rev. 1.0.1 octal t1/e1/j1 framer xy: the xth payload bit of channel y 4. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signal - ing bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/ s data stream. thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3 tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 twelfth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 242 octal t1/e1/j1 framer rev. 1.0.1 x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the receive high-speed back-plane interface should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, receive high-speed back-plane interface stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/ s data stream is thus created. the receive single-frame synchronization signal should pulse high for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0- 3. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. see figure 59 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in hmvip 16.384mbit/s mode. f igure 59. i nterfacing xrt84l38 to local t erminal e quipment using 16.384m bit / s d ata b us rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4-7 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4
xrt84l38 243 rev. 1.0.1 octal t1/e1/j1 framer the input signal timing is shown in figure 60 below when the framer is running at hmvip 16.384mbit/s mode. 5.1.3.7 t1 receive input interface - h.100 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 11, the receive back-plane interface of framer is running at h.100 16.384mbit/s mode. the hmvip mode and the h.100 mode are essential the same except for the high pulse position of the receive single-frame synchronization signal. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. the receive high-speed back-plane interface multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 1.544mbit/s ds1 data streams into this 16.384mbit/s data stream as described below: 1. the f-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. the f-bit of channel 0 is sent first, followed by f-bit of channel 1 and 2. the f-bit of channel 3 is sent last. the table below shows bit-pattern of the first octet. f igure 60. t iming d iagram of i nput signals to the f ramer when running at hmvip 16.384m bit / s first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 rxserclk (16.384mhz) rxserclk (inv) rxser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 rxsig rxsync(input) hmvip, negative sync rxsync(input) hmvip, positive sync start of frame x y : x is the bit number and y is the channel number
xrt84l38 244 octal t1/e1/j1 framer rev. 1.0.1 f x : f-bit of channel x 2. after the first octet of data is sent, the receive high-speed back-plane interface insert seven octets (fifty- six bits) of "don't care" data into the outgoing data stream. 3. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the receive high-speed back- plane interface will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how pay - load bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y 4. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signal - ing bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. ninth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 eleventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 thirteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 fifteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3
xrt84l38 245 rev. 1.0.1 octal t1/e1/j1 framer the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/ s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 5. after payload bits of timeslot 0, 1 and 2 of all four channels are sent, the terminal equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. following the same rules of step 2 to 5, the receive high-speed back-plane interface stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. a 16.384mbit/ s data stream is thus created. the receive single-frame synchronization signal should pulse high for two clock cycles (the last bit position of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0- 3. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. tenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 twelfth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 fourteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 sixteenth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 246 octal t1/e1/j1 framer rev. 1.0.1 see figure 61 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in h.100 16.384mbit/s mode. the input signal timing is shown in figure 62 below when the framer is running at h.100 16.384mbit/s mode. f igure 61. i nterfacing xrt84l38 to local t erminal e quipment using h.100 16.384m bit / s d ata b us f igure 62. t iming d iagram of i nput signals to the f ramer when running at h.100 16.384m bit / s rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4-7 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (16.384mhz) rxserclk (inv) rxser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 rxsig start of frame x y : x is the bit number and y is the channel number rxsync(input) h.100, negative sync rxsync(input) h.100, positive sync delayer h.100 rxsync(input) h.100, negative sync rxsync(input) h.100, positive sync
xrt84l38 247 rev. 1.0.1 octal t1/e1/j1 framer 6.0 the e1 transmit section 6.1 the e1 transmit payload data input interface block 6.1.1 description of the transmit payload data input interface block each of the eight framers within the xrt84l38 device includes a transmit payload data input interface block. the function of this block is to provide an interface to the local terminal equipment (for example, a central office or switching equipment) that has data to send to a "far end" terminal over a ds1 or e1 transport medium. the payload data input interface module (also known as the back-plane interface module) supports payload data to be taken from or presented to the system. in ds1 mode, supported data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. in e1 mode, supported data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the transmit payload data input interface block supplies or accepts the following signals to the local terminal equipment circuitry: ? transmit serial data input (txser_n) ? transmit serial clock (txserclk_n) ? transmit single-frame synchronization signal (txsync_n) ? transmit multi-frame synchronization signal (txmsync_n) ? transmit time-slot indicator clock (txtsclk_n) ? transmit time-slot indication bits (txtsb[4:0]_n) the transmit serial data is an input pin carrying payload, signaling and sometimes data link data supplied by the local terminal equipment to the xrt84l38 device. the transmit serial clock is an input or output signal used by the transmit payload data input interface block to latch in incoming serial data from the local terminal equipment. the transmit clock inversion bit of the transmit interface control register (ticr) determines at which edge of the transmit serial clock would data transition on the transmit serial data pin occur. the table below shows configurations of the transmit clock inversion bit of the transmit interface control register (ticr). throughout the discussion of this datasheet, we assume that serial data transition happens on rising edge of the transmit serial clock unless stated otherwise. the transmit single-frame synchronization signal is either input or output. when configured as input, it indicates the beginning of an e1 frame. when configured as output, it indicates the end of an e1 frame. the transmit multi-frame synchronization signal is either input or output. when configured as input, it indicates the beginning of an e1 multi-frame. when configure as output, it indicates the end of an e1 multi-frame. the transmit input clock signal is multiplexed into the transmit multi-frame synchronization pin (txmsync_n) of the xrt84l38. when the framer is running at high-speed back-plane interface mode, the transmit input clock functions as the timing source for the high-speed back-plane interface. transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 3 transmit clock inversion r/w 0 - serial data transition happens on rising edge of the transmit serial clock. 1 - serial data transition happens on falling edge of the transmit serial clock.
xrt84l38 248 octal t1/e1/j1 framer rev. 1.0.1 by connecting these signals with the local terminal equipment, the transmit payload data input interface accepts payload data from the terminal equipment and routes it to the transmit framer module inside the device. 6.1.2 brief discussion of the transmit payload data input interface block operating at xrt84v24 compatible 2.048mbit/s mode if the framer is operating in normal 2.048mbit/s back-plane interface mode for e1, timing source of the transmit section can be one of the three clocks: ? transmit serial input clock ? oscclk driven divided clock ? recovered receive line clock the transmit timing source select [1:0] bits of the clock select register (csr) determine which clock is used as the timing source. the following table shows configurations of the transmit timing source select [1:0] bits of the clock select register. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 1-0 transmit timing source select r/w transmit timing source select: these two read/write bit-fields permit the user to select the timing source of transmit section of the framer. when the transmit back-plane interface is operating at a clock rate of 2.048mhz for e1, these two read/write bit-fields also determine the direction of single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk). when the framer is operating at other back-plane mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. 00 - the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. 01 - the transmit serial clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchro - nization pulse (txmsync) and transmit serial clock input (txserclk) are all inputs. 10 - the oscclk driven divided clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer. 11 - the recovered receive line clock is the timing source of transmit section of the framer. when operating at the non-multiplexed 2.048mhz back-plane interface mode, the single frame synchronization pulse (txsync), multi-frame synchronization pulse (txmsync) and transmit serial clock input (txserclk) are all outputs. upon losing of the recovered receiver line clock, the oscclk driven divided clock is automatically chosen to be the timing source of the transmit section of the framer.
xrt84l38 249 rev. 1.0.1 octal t1/e1/j1 framer the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) can be either inputs or outputs depend on the timing source of the transmit section of the framer. with the oscclk driven divided clock or the recovered receive line clock being the timing source of the transmit section, the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) are all outputs. with the timing source of the transmit section being the transmit serial input clock, the transmit serial clock (txserclk_n), transmit single-frame synchronization signal (txsync_n) and transmit multi-frame synchronization signal (txmsync_n) are all inputs. the following table illustrates the input and output nature of these signals for different transmit timing sources. the transmit time-slot indication bits (txtsb[4:0]_n) are multiplexed i/o pins. the functionality of these pins is governed by the value of transmit fractional e1 input enable bit of the transmit interface control register (ticr). the following table illustrates the configurations of the transmit fractional e1 input enable bit. when configured to operate in normal condition (that is, when the transmit fractional e1 input enable bit is equal to zero), these bits reflect the five-bit binary value of the time slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. txtsb[4] represents the msb of the binary value and txtsb[0] represents the lsb. t ransmit t iming s ource t x s er c lk _ n t x s ync _ n t x ms ync _ n terminal equipment driven txserclk input input input oscclk driven divided clock output output output recovered receive line clock output output output transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 transmit fractional e1 input enable r/w 0 - the transmit time-slot indication bits (txtsb[4:0] are outputting five-bit binary values of time-slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. the transmit time-slot indicator clock signal (txtsclk_n) is a 256khz clock that pulses high for one e1 bit period whenever the transmit payload data input interface block is accepting the lsb of each of the twenty-four time slots. 1 - the txtsb[0]_n bit becomes the transmit fractional e1 input signal (txfrtd_n) which carries fractional e1 payload data into the framer. the txtsb[1]_n bit becomes the transmit signaling data input signal (txsig_n) which is used to insert robbed-bit signaling data into the outbound e1 frame. the txtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. the txtsb[3]_n bit becomes the transmit overhead synchronization pulse (txohsync_n) which is used to output an overhead synchronization pulse that indicates the first bit of each e1multi-frame. the txtsclk_n will output gaped fractional e1 clock that can be used by termi - nal equipment to clock out fractional e1 payload data at rising edge of the clock. or, the txtsclk_n pin will be a clock enable signal to transmit fractional e1 input signal (txfrtd_n) when the un-gaped transmit serail input clock (txserclk_n) is used to clock in fractional e1 payload data into the framer.
xrt84l38 250 octal t1/e1/j1 framer rev. 1.0.1 when the transmit fractional e1 input enable bit is equal to one, the txtsb[0]_n bit becomes the transmit fractional e1 input signal (txfrtd_n). this input pin carries fractional e1 input data to be inserted into the outbound e1 data stream. the fraction e1 input interface allows certain time-slots of outbound e1 data stream to have a different source other than the local terminal equipment. function of the fractional e1 input signal will be discussed in details in later sections. when the transmit fractional e1 input enable bit is equal to one, the txtsb[1]_n bit becomes the transmit signaling data input signal (txsig_n). these input pins can be used to insert robbed-bit signaling data into the outbound e1 frame. function of the transmit signaling data input signal will be discussed in details in later sections. when the transmit fractional e1 input enable bit is equal to one, the txtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-31) being accepted and processed by the transmit payload data input interface block of the framer. msb of the binary value is presented first and the lsb is presented last. when the transmit fractional e1 input enable bit is equal to one, the txtsb[3]_n bit becomes the transmit overhead synchronization pulse (txohsync_n). these pins can be used to output an overhead synchronization pulse that indicates the first bit of each e1multi-frame. function of the transmit overhead synchronization output signal will be discussed in details in later sections. the txtsb[4]_n bit is not multiplexed. the table below shows functionality of the txtsb[3:0] bits when the transmit fractional e1 input bit is set to different values. the transmit time-slot indicator clock signal (txtsclk_n) is a multi-function output pin. when configured to operate in normal condition (that is, when the transmit fractional e1 input enable bit is equal to zero), the txtsclk_n is a 256khz clock that pulses high for one e1 bit period whenever the transmit payload data input interface block is accepting the lsb of each of the twenty-four time slots. the local terminal equipment should use this clock signal to sample the txtsb[0] through txtsb[4] bits and identify the time-slot being processed via the transmit section of the framer. when the transmit fractional e1 input enable bit is equal to one, the txtsclk_n will output gaped fractional e1 clock at time-slots where fractional e1 input data is present. this clock can be used by terminal equipment to clock out fractional e1 payload data at rising edge of the clock. the framer will then input fractional e1 payload data using falling edge of the clock. otherwise, this pin can be configured as a clock enable signal to transmit fractional e1 input signal (txfrtd_n) if the framer is set accordingly. in this way, fractional e1 payload data is clocked into the framer using un-gaped transmit serail input clock (txserclk_n). a detailed discussion of the fractional e1 payload data input interface can be found in later sections. both the transmit time-slot indicator clock (txtsclk_n) and the transmit time-slot indication bits (txtsbb[4:0]_n) are output signals in normal 2.048mbit/s back-plane mode regardless of the timing source of the transmit section of framer. a detailed discussion of how to connect the transmit payload data input interface block to the local terminal equipment using different timing sources can be found in the later sections. 6.1.2.1 connect the transmit payload data input interface block to the local terminal equipment if transmit timing source = txserclk_n by setting the transmit timing source [1:0] bits of the clock select register to 01, the txserclk_n input signal is configured to be the timing source for the transmit section of the framer. the terminal equipment should t ransmit f ractional e1 i nput b it = 0 t ransmit f ractional e1 i nput b it = 1 txtsb[0] output txfrtd input txtsb[1] output txsig input txtsb[2] output txts output txtsb[3] output txohsync output
xrt84l38 251 rev. 1.0.1 octal t1/e1/j1 framer supply an external free-running clock with frequency of 2.048mhz to the txserclk_n input pin. the transmit single-frame synchronization signal and the transmit multi-frame synchronization signal are inputs to the framer. the transmit single-frame synchronization signal should pulse high for one e1 bit period (488ns) at the first bit position of each e1 frame. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of an e1 frame. the transmit multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the first bit position of the first frame of an e1 multi-frame. by sampling the high pulse on the transmit multi-frame synchronization signal, the framer can position the beginning of an e1 super-frame. it is the responsibility of the terminal equipment to provide serial input data through the txser_n pin aligned with the transmit single-frame synchronization signal and the transmit multi-frame synchronization signal. see figure 63 below for how to connect the transmit payload data input interface block to the local terminal equipment with the transmit serial clock being the timing source of transmit section. f igure 63. i nterfacing xrt84l38 to local terminal equipment with t x s er c lk _ n as t ransmit t iming s ource txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 252 octal t1/e1/j1 framer rev. 1.0.1 the following figure 64 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connecting the transmit payload data input interface block to the local terminal equipment with the transmit serial clock being the timing source of transmit section. 6.1.2.2 connect the transmit payload data input interface block to the local terminal equipment if the transmit timing source = oscclk by setting the transmit timing source [1:0] bits of the clock select register (csr) to 10, the oscclk driven divided clock is configured to be the timing source for the transmit section of the framer. a free-running clock should apply to the oscclk input pin with frequencies of 16.384mhz, 32.768mhz and 65.536mhz depending on the setting of oscclk frequency select [1:0] bits of the clock select register (csr). the free-running oscclk is divided inside the xrt84l38 and routed to all eight framers. this oscclk driven divided clock has to be 16.384mhz in frequency. when these bits are set to 00, the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 16.384mhz. when these bits are set to 01, the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 32.768mhz. when these bits are set to 10, the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 65.536mhz. f igure 64. w aveforms of the signals that connect the t ransmit p ayload d ata i nput i nterface b lock to the local t erminal e quipment with the t ransmit s erial clock being the timing source of the t rans - mit s ection c txserclk txserclk (inv) txser txsync(input) txsync(output) txchclk txchn[4:0] txchn[0]/txsig txtsb[4:0] txtsclk txchn[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d
xrt84l38 253 rev. 1.0.1 octal t1/e1/j1 framer the following table shows configurations of the oscclk frequency select [1:0] bits of the clock select register. the transmit serial clock signal pin (txserclk_n) is output from the framer. the framer outputs a 2.048mhz clock through this pin to the local terminal equipment. the transmit single-frame synchronization signal and the transmit multi-frame synchronization signal are also automatically configured to be output signals. the transmit single-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of each e1 frame. by triggering on the high pulse on the transmit single-frame synchronization signal, the local terminal equipment can identify the end of an e1 frame and should start inserting payload data of the next e1 frame to the framer. the transmit multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of the last frame of an e1 multi-frame. by triggering on the high pulse on the transmit multi-frame synchronization signal, the local terminal equipment can identify the end of an e1 super-frame and should start inserting payload data of the next e1 multi-frame into the framer. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 3-2 oscclk frequency select r/w these two read/write bit-fields permit the user to select internal clock divid - ing logic of the framer depending on the frequency of incoming oscillator clock (oscclk). the frequency of internal clock used by the framer should be 16.384mhz. 00 - the framer will internally divide the incoming oscclk by one. therefore, the external oscillator clock applied to the oscclk pin should be 16.384mhz. 01 - the framer will internally divide the incoming oscclk by two. therefore, the external oscillator clock applied to the oscclk pin should be 32.768mhz. 10 - the framer will internally divide the incoming oscclk by four. therefore, the external oscillator clock applied to the oscclk pin should be 65.536mhz.
xrt84l38 254 octal t1/e1/j1 framer rev. 1.0.1 see figure 65 for how to connect the transmit payload data input interface block to the local terminal equipment with the oscclk driven divided clock as the timing source of transmit section. f igure 65. i nterfacing xrt84l38 to local terminal equipment with oscclk driven divided clock as transmit timing source txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 oscclk oscclk driven divided clock
xrt84l38 255 rev. 1.0.1 octal t1/e1/j1 framer the following figure 66 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connecting the transmit payload data input interface block to the local terminal equipment with the oscclk driven divided clock as the timing source of transmit section. 6.1.2.3 connect the transmit payload data input interface block to the local terminal equipment for loop-timing applications if the transmit timing source [1:0] bits of the clock select register are set to 00 or 11, the recovered receive line clock is configured to be the timing source for the transmit section of the framer. this is also known as the loop-timing mode. if the clock loss detection enable bit of the clock select register is set to one, and if the recovered receive line clock from the liu is lost, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. f igure 66. w averforms of the signals connecting the t ransmit p ayload d ata i nput i nterface block to the local t erminal e quipment with the oscclk driven divided clock as the timing source of the t ransmit s ection c txserclk txserclk (inv) txser txsync(output) txchclk txchn[4:0] txchn[0]/txsig txchclk txchn[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d txchn[0]/txsig
xrt84l38 256 octal t1/e1/j1 framer rev. 1.0.1 the following table shows configuration of the clock loss detection enable bit of the clock select register (csr). the transmit serial clock signal pin (txserclk_n) is output from the framer. the xrt84l38 device routes the recovered receive line clock internally across the framer and output through the transmit serial clock signal pin to the local terminal equipment. the transmit single-frame synchronization signal and the transmit multi- frame synchronization signal are automatically configured to be output signals. the transmit single-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of each e1 frame. by triggering on the high pulse on the transmit single-frame synchronization signal, the local terminal equipment can identify the end of an e1 frame and should start inserting payload data of the next e1 frame to the framer. the transmit multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of the last frame of an e1 multi-frame. by triggering on the high pulse on the transmit multi-frame synchronization signal, the local terminal equipment can identify the end of an e1 super-frame and should start inserting payload data of the next e1 multi-frame into the framer. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 4 clock loss detection enable r/w this read/write bit-field permits the user to enable the clock loss detection logic for the framer when the recovered receive line clock is used as transmit timing source of the framer. 0 - the framer disables the clock loss detection logic. 1 - the framer enables the clock loss detection logic. if the recovered receive line clock is used as transmit timing source of the framer, and if clock recovered from the liu is lost, the framer can detect loss of the recovered receive line clock. upon detecting of this occurrence, the framer will automatically begin to use the oscclk driven divided clock as transmit timing source until the liu is able to regain clock recovery. n ote : this bit-field is ignored if the txserclk or the oscclk driven divided clock is chosen to be the timing source of transmit section of the framer.
xrt84l38 257 rev. 1.0.1 octal t1/e1/j1 framer see figure 67 for how to connect the transmit payload data input interface block to the local terminal equipment with the recovered receive line clock being the timing source of transmit section. f igure 67. i nterfacing xrt84l38 to local terminal equipment with recovered receive line clock as transmit timing source txserclk_0 txser_0 txmsync_0 txsync_0 txtsclk_0 txtsb[4:0]_0 txserclk_7 txser_7 txmsync_7 txsync_7 txtsclk_7 txtsb[4:0]_7 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 rxlineclk_0 rxlineclk_7
xrt84l38 258 octal t1/e1/j1 framer rev. 1.0.1 the following figure 68 shows waveforms of the signals (txserclk_n, txser_n, txsync_n, txtsclk_n and txtsb[4:0]_n) that connecting the transmit payload data input interface block to the local terminal equipment with the recovered receive line clock being the timing source of transmit section. 6.1.3 brief discussion of the transmit high-speed back-plane interface the high-speed back-plane interface supports payload data to be taken from or presented to the terminal equipment at different data rates. in e1 mode, supported high-speed data rates are mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the transmit multiplex enable bit and the transmit interface mode select [1:0] bits of the transmit interface control register (ticr) determine the transmit back-plane interface data rate. the following table shows configurations of the transmit multiplex enable bit and the transmit interface mode select [1:0] bits of the transmit interface control register (ticr). f igure 68. w averforms of the signals connecting the t ransmit p ayload d ata input interface block to the local t erminal e quipment with the r ecovered r eceive l ine c lock being the timing source of transmit section transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 2 transmit multiplex enable r/w 0 - the transmit back-plane interface block is configured to non-channel-multi - plexed mode 1 - the transmit back-plane interface block is configured to channel-multiplexed mode 1-0 transmit interface mode select r/w when combined with the transmit multiplex enable bit, these bits determine the transmit back-plane interface data rate. c txserclk txserclk (inv) txser txsync(output) txchclk txchn[4:0] txchn[0]/txsig txchclk txchn[1]/txfrtd f f c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 input data input data input data input data timeslot #0 timeslot #5 timeslot #6 timeslot #23 timeslot 23 timeslot 0 timeslot 5 timeslot 6 a b d c a b d c a b d c a b d txchn[0]/txsig
xrt84l38 259 rev. 1.0.1 octal t1/e1/j1 framer the table below shows the combinations of transmit multiplex enable bit and transmit interface mode select [1:0] bits and the resulting transmit back-plane interface data rates. when the transmit multiplex enable bit is set to zero, the framer is configured in non-channel-multiplexed mode. the possible data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s. in non-channel-multiplexed mode, payload data of each channel are taken from the terminal equipment separately. each channel uses its own transmit serial clock, transmit serial data, transmit single-frame synchronization signal and transmit multi-frame synchronization signal as interface between the framer and the terminal equipment. section 1.1.2.1, 1.1.2.2 and 1.1.2.3 provide details on how to connect the transmit payload data interface block with the terminal equipment when the back-plane interface data rate is 1.544mbit/s. when the back-plane interface data rate is mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s, the transmit serial clock, transmit serial data, transmit single-frame synchronization signal and transmit multi-frame synchronization signal are all configured as inputs. the transmit serial clock is always an input clock with frequency of 2.048 mhz for all data rates. the txmsync_n signal is configured as the transmit input clock with frequencies of 2.048 mhz, 4.096 mhz and 8.192 mhz respectively. it serves as the primary clock source for the high-speed back-plane interface. the table below summaries the clock frequencies of txserclk_n and txinclk_n inputs when the framer is operating in non-multiplexed high-speed back-plane mode. when the transmit multiplex enable bit is set to one, the framer is configured in channel-multiplexed mode. the possible data rates are bit-multiplexed 16.384mbit/s, hmvip 16.384mbit/s and h.100 16.384mbit/s. in channel-multiplexed mode, every four channels share the transmit serial data and transmit single-frame synchronization signal of one channel as interface between the framer and the local terminal equipment. the txmsync_n signal of one channel is configured as the transmit input clock with frequencies of 16.384 mhz. it serves as the primary clock source for the high-speed back-plane interface. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. the t ransmit m ultiplex e nable b it t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate 0 0 0 xrt84v24 compatible 2.048mbit/s 0 0 1 mvip 2.048mbit/s 0 1 0 4.096mbit/s 0 1 1 8.192mbit/s 1 0 0 - 1 0 1 bit multiplexed 16.384mbit/s 1 1 0 hmvip 16.384mbit/s 1 1 1 h.100 16.384mbit/s transmit multiplex enable bit = 0 t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate t x s er c lk t x ms ync /t x i n c lk 0 0 2.048mbit/s 2.048 mhz - 0 1 mvip 2.048mbit/s 2.048 mhz 2.048 mhz 1 0 4.096mbit/s 2.048 mhz 4.096 mhz 1 1 8.192mbit/s 2.048 mhz 8.192 mhz
xrt84l38 260 octal t1/e1/j1 framer rev. 1.0.1 transmit single-frame synchronization signal of channel 0 pulses high at the beginning of the frame with data from channel 0-3 multiplexed together. the transmit single-frame synchronization signal of channel 4 pulses high at the beginning of the frame with data from channel 4-7 multiplexed together. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. additionally, each channel requires the local terminal equipment to provide a free- running 2.048 mhz clock into the transmit serial clock input. the table below summaries the clock frequencies of txserclk_n and txinclk_n inputs when the framer is operating in multiplexed high-speed back-plane mode. the transmit serial clock is always running at 1.544mhz for all the high-speed back-plane interface modes. it is automatically the timing source of the transmit section of the framer in high-speed back-plane interface mode. the transmit single-frame synchronization signal should pulse high or low for one bit period at the first bit position of each e1 frame. length of the bit period depends on data rate of the high-speed back-plane interface. the transmit synchronization pulse low bit of the transmit interface control register (ticr) determines whether the transmit single-frame synchronization signal is high active or low active. the table below shows configurations of the transmit synchronization pulse low bit of the transmit interface control register (ticr). throughout the discussion of this datasheet, we assume that the transmit single-frame synchronization signal pulses high unless stated otherwise. the txmsync_n signal, which is a multiplexed i/o pin, no longer functions as the transmit multi-frame synchronization signal. indeed, it becomes the transmit input clock signal (txinclk) of the high-speed back- plane interface of the framer. the local terminal equipment should provide a free-running clock with the same frequency as the high-speed back-plane interface to this input pin. the following sections discuss details of how to operate the framer in different back-plane interface speed mode and how to connect the transmit payload data input interface block to the local terminal equipment. 6.1.3.1 e1 transmit input interface - mvip 2.048 mhz when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 01, the transmit back-plane interface of framer is running at a data rate of 2.048mbit/s. transmit multiplex enable bit = 1 t ransmit i nterface m ode s elect b it 1 t ransmit i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate t x s er c lk t x ms ync /t x c lk 0 0 - - - 0 1 bit-multiplexed 16.384mbit/s 2.048 mhz 16.384 mhz 1 0 hmvip 16.384mbit/s 2.048 mhz 16.384 mhz 1 1 h.100 16.384mbit/s 2.048 mhz 16.384 mhz transmit interface control register (ticr) (ndirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 3 transmit synchronization pulse low r/w 0 - the transmit single-frame synchronization signal will pulse high indicat - ing the beginning of an e1 frame when the high-speed back-plane interface is running at a mode other than the xrt84v24 compatible 2.048mbit/s. 1 - the transmit single-frame synchronization signal will pulse low indicat - ing the beginning of an e1 frame when the high-speed back-plane interface is running at a mode other than the xrt84v24 compatible 2.048mbit/s.
xrt84l38 261 rev. 1.0.1 octal t1/e1/j1 framer the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_n at 2.048mbit/s. the local terminal equipment supplies a free-running 2.048mhz clock to he transmit input clock pin of the framer. the local terminal equipment also provides synchronized payload data at rising edge of the clock. the transmit high- speed back-plane interface of the framer then latches incoming serial data at falling edge of the transmit input clock. the transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of an e1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. see figure 69 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in mvip 2.048mbit/s mode. f igure 69. i nterfacing xrt84l38 to local terminal equipment using mvip 2.048m bit / s data bus txserclk_0 txser_0 txinclk_0 (2.048mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (2.048mhz) txsync_7
xrt84l38 262 octal t1/e1/j1 framer rev. 1.0.1 the timing diagram of input signals to the framer when running at mvip 2.048mbit/s mode is shown in figure 70 . 6.1.3.2 e1 transmit input interface - 4.096 mhz (this interface mode is the same as running at 2.048 mhz. the only difference is that the transmit input clock runs two times faster at 4.096 mhz) when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 10, the transmit back-plane interface of framer is running at a clock rate of 4.096mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is still accepting data through txser_n at an e1 equivalent data rate of 2.048mbit/s. however, the local terminal equipment supplies a free-running 4.096mhz clock to the transmit input clock pin of the framer. the local terminal equipment provides synchronized payload data at every other rising edge of the transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at every other falling edge of the clock. transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of an e1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. f igure 70. t iming diagram of input signals to the framer when running at mvip 2.048m bit / s txserclk txserclk (inv) txser txsync(input) txsync(input) mvip mode txchclk txchn[0]/txsig txsyncfrd=0 txchn[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care don't care c a b d don't care don't care note: the following signals are not aligned with the signals shown above. the txchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txchn[1]/txfrtd txchclk txsyncfrd=1
xrt84l38 263 rev. 1.0.1 octal t1/e1/j1 framer see figure 71 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in 4.096mbit/s mode. the timing diagram of input signals to the framer when running at 4.096mbit/s mode is shown in figure 72 . 6.1.3.3 e1 transmit input interface - 8.192 mhz (this interface mode is the same as running at 2.048 mhz. the only difference is that the transmit input clock runs four times faster at 8.192mhz) when the transmit multiplex enable bit is set to zero and the transmit interface mode select [1:0] bits are set to 11, the transmit back-plane interface of framer is running at a clock rate of 8.192mhz. the interface consists of the following pins: f igure 71. i nterfacing xrt84l38 to local terminal equipment using 4.096m bit / s data bus f igure 72. t iming diagram of input signals to the framer when running at 4.096m bit / s mode txserclk_0 txser_0 txinclk_0 (4.096mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (4.096mhz) txsync_7 txserclk (2mhz) txserclk (inv) txser txsync(input) txchclk(inv) txchn[0]/txsig txchn[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txserclk (4mhz) don't care don't care
xrt84l38 264 octal t1/e1/j1 framer rev. 1.0.1 ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is still accepting data through txser_n at an e1 equivalent data rate of 2.048mbit/s. however, the local terminal equipment supplies a free-running 8.192mhz clock to the transmit input clock pin of the framer. the local terminal equipment provides synchronized payload data at every other four rising edge of the transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at every other four falling edge of the clock. the transmit single-frame synchronization input signal (txsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of an e1 frame. it is responsibility of the local terminal equipment to align the transmit single-frame synchronization signal with serial data stream going into the framer. see figure 73 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in 8.192mbit/s mode. f igure 73. i nterfacing xrt84l38 to local terminal equipment using 8.192m bit / s data bus txserclk_0 txser_0 txinclk_0 (8.192mhz) txsync_0 transmit payload data input interface chn 0 transmit payload data input interface chn 7 terminal equipment xrt84l38 txserclk_7 txser_7 txinclk_7 (8.192mhz) txsync_7
xrt84l38 265 rev. 1.0.1 octal t1/e1/j1 framer the timing diagram of input signals to the framer when running at 8.192mbit/s mode is shown in figure 74 . 6.1.3.4 e1 transmit input interface - bit-multiplexed 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 01, the transmit back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. f igure 74. t iming diagram of input signals to the framer when running at 8.192m bit / s mode t xserclk (2mhz) t xserclk (inv) t xser t xsync(input) t xchclk(inv) t xchn[0]/txsig t xchn[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 t xserclk (8mhz) don't care don't care
xrt84l38 266 octal t1/e1/j1 framer rev. 1.0.1 after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y 2. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3 fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3
xrt84l38 267 rev. 1.0.1 octal t1/e1/j1 framer x y : the xth payload bit of channel y a y : the signaling bit a of channel y 3. after the first octet of all four channels are sent, the local terminal equipment start sending the second octets following the same rules of step 1 and 2. the transmit single-frame synchronization signal of channel 0 pulses high for one clock cycle at the first bit position of the data stream with data from channel 0-3 multiplexed together. the transmit single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed e1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 device and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 1.544mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. see figure 75 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in bit-multiplexed 16.384mbit/s mode. eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 268 octal t1/e1/j1 framer rev. 1.0.1 the input signal timing is shown in figure 76 below when the framer is running at bit-multiplexed 16.384mbit/ s mode. 6.1.3.5 e1 transmit input interface - hmvip 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 10, the transmit back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) f igure 75. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus f igure 76. iming signal when the framer is running at b it -m ultiplexed 16.384m bit / s mode txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (16.384mhz) txserclk (inv) txser txsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 56 cycles
xrt84l38 269 rev. 1.0.1 octal t1/e1/j1 framer ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equipment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 third octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3
xrt84l38 270 octal t1/e1/j1 framer rev. 1.0.1 2. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 3. after the first octet of all four channels are sent, the local terminal equipment start sending the second octets following the same rules of step 1 and 2. the transmit single-frame synchronization signal should pulse high for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the transmit single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the transmit single-frame synchronization signal of channel 4 pulses high to identify the start of multiplexed data stream of channel 4- 7. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed e1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 fourth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 271 rev. 1.0.1 octal t1/e1/j1 framer inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 device and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 2.048mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. see figure 77 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in hmvip 16.384mbit/s mode. the input signal timing is shown in figure 78 below when the framer is running at hmvip 16.384mbit/s mode. 6.1.3.6 e1 transmit input interface - h.100 16.384mbit/s when the transmit multiplex enable bit is set to one and the transmit interface mode select [1:0] bits are set to 11, the transmit back-plane interface of framer is running at h.100 16.384mbit/s mode. f igure 77. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus f igure 78. t iming s ignal when the framer is running at hmvip 16.384m bit / s mode txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (1.544mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (1.544mhz) txserclk_2 (1.544mhz) txserclk_3 (1.544mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (1.544mhz) txserclk_5 (1.544mhz) txserclk_6 (1.544mhz) txserclk_7 (1.544mhz) txserclk (16.384mhz) txserclk (inv) txser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 txsig txsync(input) hmvip, negative sync txsync(input) hmvip, positive sync start of frame x y : x is the bit number and y is the channel number
xrt84l38 272 octal t1/e1/j1 framer rev. 1.0.1 (the hmvip mode and the h.100 mode are essential the same except for the high pulse position of the transmit single-frame synchronization signal) the interface consists of the following pins: ? data input (txser_n) ? transmit serial clock input signal (txserclk_n) ? transmit single-frame synchronization input signal (txsync_n) ? transmit input clock (txinclk_n) ? transmit time-slot indication clock (txtsclk_n) ? transmit time slot indicator bits (txtsb[4:0]_n) the transmit back-plane interface is accepting data through txser_0 or txser_4 pins at 16.384mbit/s. the local terminal equipment multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the transmit serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the transmit serial data pin of channel 4. free-running clocks of 16.384mhz is supplied to the transmit input clock pin of channel 0 and channel 4 of the framer. the local terminal equipment provides multiplexed payload data at rising edge of this transmit input clock. the transmit high-speed back-plane interface of the framer then latches incoming serial data at falling edge of the clock. the local terminal equipment maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equipment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 third octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2
xrt84l38 273 rev. 1.0.1 octal t1/e1/j1 framer x y : the xth payload bit of channel y 2. the local terminal equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the terminal equipment is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3 second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 fourth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 274 octal t1/e1/j1 framer rev. 1.0.1 3. after the first octet of all four channels are sent, the local terminal equipment start sending the second octets following the same rules of step 1 and 2. the transmit single-frame synchronization signal should pulse high for two clock cycles (the last bit position of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the transmit single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the transmit single-frame synchronization signal of channel 4 pulses high to identify the start of multiplexed data stream of channel 4- 7. by sampling the high pulse on the transmit single-frame synchronization signal, the framer can position the beginning of the multiplexed e1 frame. it is responsibility of the terminal equipment to align the multiplexed transmit serial data with the transmit single-frame synchronization pulse. inside the framer, all the "don't care" bits will be stripped away. the framing bits, signaling and payload data are de-multiplexed inside the xrt84l38 device and send to each individual channel. these data will be processed by each individual framer and send to liu interface. the local terminal equipment provides a free-running 2.048mhz clock to the transmit serial input clock of each channel. the framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. see figure 79 below for how to interface the local terminal equipment with the transmit payload data input interface block of the framer in hmvip 16.384mbit/s mode. f igure 79. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus txser_0 txinclk_0 (16.384mhz) txsync_0 txserclk_0 (2.048mhz) transmit payload data input interface chn 0 transmit payload data input interface chn 4 terminal equipment xrt84l38 chn 1 chn 2 chn 3 chn 5 chn 6 chn 7 txserclk_1 (2.048mhz) txserclk_2 (2.048mhz) txserclk_3 (2.048mhz) txser_4 txinclk_4 (16.384mhz) txsync_4 txserclk_4 (2.048mhz) txserclk_5 (2.048mhz) txserclk_6 (2.048mhz) txserclk_7 (2.048mhz)
xrt84l38 275 rev. 1.0.1 octal t1/e1/j1 framer the input signal timing is shown in figure 80 below when the framer is running at h.100 16.384mbit/s mode. the e1 receive section 6.2 the receive payload data output interface block 6.2.1 description of the receive payload data output interface block each of the eight framers within the xrt84l38 device includes a receive payload data output interface block. the function of the block is to provide an interface to the terminal equipment (for example, a central office or switching equipment) that has data to receive from a "far end" terminal over an ds1 or e1 transport medium. the payload data output interface module (also known as the back-plane interface module) supports payload data to be taken from or presented to the system. in e1 mode, supported data rates are 1.544mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 12.352mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. in e1 mode, supported data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the receive payload data output interface block supplies or accepts the following signals to the terminal equipment circuitry: ? receive serial data input (rxser_n) ? receive serial clock (rxserclk_n) ? receive single-frame synchronization signal (rxsync_n) ? receive multi-frame synchronization signal (rxmsync_n) ? receive time-slot indicator clock (rxtsclk_n) ? receive time-slot indication bits (rxtsb[4:0]_n) the receive serial data is an output pin carrying payload, signaling and sometimes data link data supplied by xrt84l38 device to the local terminal equipment. the receive serial clock is an input or output signal used by the receive payload data input interface block to send out serial data to the local terminal equipment. the receive clock inversion bit of the receive interface control register (ticr) determines at which edge of the receive serial clock would data transition on the receive serial data pin occur. f igure 80. t iming signal when the framer is running at h.100 16.384m bit / s mode txserclk (16.384mhz) txserclk (inv) txser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 txsig start of frame x y : x is the bit number and y is the channel number txsync(input) h.100, negative sync txsync(input) h.100, positive sync delayer h.100 txsync(input) h.100, negative sync txsync(input) h.100, positive sync
xrt84l38 276 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the receive clock inversion bit of the receive interface control register (ricr). throughout the discussion of this datasheet, we assume that serial data transition happens on rising edge of the receive serial clock unless stated otherwise. the receive single-frame synchronization signal is either input or output. when configure as input, it indicates beginning of an e1 frame. when configure as output, it indicates end of an e1 frame. the receive multi-frame synchronization signal is an output pin from xrt84l38 indicating end of an e1 multi- frame. by connecting these signals with the local terminal equipment, the receive payload data output interface routes received payload data from the receive framer module to the local terminal equipment. 6.2.2 brief discussion of the receive payload data output interface block operating at xrt84v24 compatible 2.048mbit/s mode the incoming receive payload data is taken into the framer from the liu interface using the recovered receive line clock. the payload data is then routed through the receive farmer module and presented to the receive payload data output interface through the receive serial data output pin (rxser_n). this data is then clocked out using the receive serial clock (rxserclk_n). there is a two-frame (512 bits) elastic buffer between the receive framer module and the receive payload data output interface. this buffer can be enabled or disabled via programming the slip buffer enable [1:0] bits in slip buffer control register (sbcr). the following table shows configurations of the slip buffer enable [1:0] bits in slip buffer control register. if the slip buffer is not in bypass mode, then the user has the option of either providing the receive single- frame synchronization pulse or getting the receive single-frame synchronization pulse on frame boundary at the rxsync_n pin. the slip buffer receive synchronization direction bit of the slip buffer control register (sbcr) determines whether the receive single-frame synchronization signal is input or output. the table receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 3 receive clock inversion r/w 0 - serial data transition happens on rising edge of the receive serial clock. 1 - serial data transition happens on falling edge of the receive serial clock. slip buffer control register (sbcr) (indirect address = 0xn0h, 0x16h) b it n umber b it n ame b it t ype b it d escription 1-0 slip buffer enable r/w 00 - slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output. 01 - the elastic store (slip buffer) is enabled. the receive payload data is passing from the receive framer module through the slip buffer to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. 10 - the slip buffer acts as a fifo. the fifo latency register (flr) deter - mines the data latency. the receive payload data is passing from the receive framer module through the fifo to the receive payload data output interface. the receive serial clock signal (rxserclk_n) is an input. 11 - slip buffer is bypassed. the receive payload data is passing from the receive framer module to the receive payload data output interface directly without routing through the slip buffer. the receive serial clock signal (rxserclk_n) is an output.
xrt84l38 277 rev. 1.0.1 octal t1/e1/j1 framer below demonstrates settings of the slip buffer receive synchronization direction bit of the slip buffer control register. if the slip buffer is in bypass mode, the receive payload data is routed to the receive payload data output interface from the receive framer module directly. the recovered line clock is used to carry the receive payload data all the way from the liu interface, to the receive framer module and eventually output through the receive serial data output pin. the receive serial clock signal is therefore an output using the recovered receive line clock as timing source. the receive single-frame synchronization signal is also output in slip buffer bypass mode. if the slip buffer is enabled, the receive payload data is latched into the elastic store using the recovered receive line clock. the local terminal equipment supplies a free-running 2.048mhz clock to the receive serial clock pin to latch the receive payload data out from the elastic store. since the recovered receive line clock and the receive serial clock are coming from different timing sources, the slip buffer will gradually fill or empty. if the elastic buffer either fills or empties, a controlled slip will occur. if the buffer empties and a read occurs, then a full frame of data will be repeated and a status bit will be updated. if the buffer fills and a write comes, then a full frame of data will be deleted and another status bit will be set. a detailed description of the elastic buffer can be found in later sections. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. if the slip buffer is put into a fifo mode, it is acting like a standard first-in-first-out storage. a fixed read and write latency is maintained in a programmable fashion controlled by the fifo latency register (fifolr). the local terminal equipment supplies a 2.048mhz clock to the receive serial clock pin to latch the receive payload data out from the fifo. however, it is the responsibility of the user to phase lock the input receive serial clock to the recovered receive line clock to avoid either over-run or under-run of the fifo. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. the following table summaries the input or output nature of the receive serial clock and receive single- frame synchronization signals for different slip buffer settings. slip buffer control register (sbcr) (indirect address = 0xn0h, 0x16h) b it n umber b it n ame b it t ype b it d escription 2 slip buffer receive synchronization direction r/w 0 - the receive single-frame synchronization signal (rxsync_n) is an output if the slip buffer is not in bypass mode. 1 - the receive single-frame synchronization signal (rxsync_n) is an input if the slip buffer is not in bypass mode. r eceive t iming s ource r x s er c lk _ n r x s ync _ n slip buffer synchronization direction bit = 0 slip buffer synchronization direction bit = 1 slip buffer bypassed output output output slip buffer enabled input output input slip buffer acts as fifo input output input
xrt84l38 278 octal t1/e1/j1 framer rev. 1.0.1 the receive time-slot indication bits (rxtsb[4:0]_n) are multiplexed i/o pins. the functionality of these pins is governed by the value of receive fractional e1 output enable bit of the receive interface control register (ricr). the following table illustrates the configurations of the receive fractional e1 input enable bit. when configured to operate in normal condition (that is, when the receive fractional e1 input enable bit is equal to zero), these bits reflect the five-bit binary value of the time slot number (0-31) being outputted and processed by the receive payload data output interface block of the framer. rxtsb[4] represents the msb of the binary value and rxtsb[0] represents the lsb. when the receive fractional e1 output enable bit is equal to one, the rxtsb[0]_n bit becomes the receive fractional e1 output signal (rxfrtd_n). this output pin carries fractional e1 output data extracted by the framer from the incoming e1 data stream. the fractional e1 output interface allows certain time-slots of e1 data to be routed to destinations other than the local terminal equipment. function of the fractional e1 output signal will be discussed in details in later sections. when the receive fractional e1 output enable bit is equal to one, the rxtsb[1]_n bit becomes the receive signaling data output signal (rxsig_n). these output pins can be used to carry robbed-bit signaling data extracted from the inbound e1 frame. function of the receive signaling data output signal will be discussed in details in later sections. when the receive fractional e1 output enable bit is equal to one, the rxtsb[2]_n bit serially outputs all five- bit binary values of the time slot number (0-31) being outputted and processed by the receive payload data output interface block of the framer. msb of the binary value is presented first and the lsb is presented last. the rxtsb[3]_n and rxtsb[4}_n pins are not multiplexed. the table below shows functionality of the rxtsb[2:0] bits when the receive fractional e1 output bit is set to different values. receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 4 receive fractional e1 output enable r/w 0 - the receive time-slot indication bits (rxtsb[4:0] are outputting five-bit binary values of time-slot number (0-31) being accepted and processed by the receive payload data output interface block of the framer. the receive time-slot indicator clock signal (rxtsclk_n) is a 256khz clock that pulses high for one e1 bit period whenever the receive payload data out - put interface block is accepting the lsb of each of the twenty-four time slots. 1 - the rxtsb[0]_n bit becomes the receive fractional e1 output signal (rxfrtd_n) which carries fractional e1 payload data from the framer. the rxtsb[1]_n bit becomes the receive signaling data output signal (rxsig_n) which is used to carry robbed-bit signaling data extracted from the inbound e1 frame. the rxtsb[2]_n bit serially outputs all five-bit binary values of the time slot number (0-31) being accepted and processed by the receive payload data out - put interface block of the framer. the rxtsclk_n will output gaped fractional e1 clock that can be used by termi - nal equipment to latch in fractional e1 payload data at rising edge of the clock. or, the rxtsclk_n pin will be a clock enable signal to receive fractional e1 output signal (rxfrtd_n) when the un-gaped receive serail output clock (rxserclk_n) is used to latch in fractional e1 payload data into the terminal equipment. r eceive f ractional e1 o utput b it = 0 r eceive f ractional e1 o utput b it = 1 rxtsb[0] output rxfrtd output
xrt84l38 279 rev. 1.0.1 octal t1/e1/j1 framer the receive time-slot indicator clock signal (rxtsclk_n) is a multi-function output pin. when configured to operate in normal condition (that is, when the receive fractional e1 input enable bit is equal to zero), the rxtsclk_n is a 256khz clock that pulses high for one e1 bit period whenever the receive payload data output interface block is outputting the lsb of each of the twenty-four time slots. the local terminal equipment should use this clock signal to sample the rxtsb[0] through rxtsb[4] bits and identify the time-slot being processed via the receive section of the framer. when the receive fractional e1 output enable bit is equal to one, the rxtsclk_n will output gaped fractional e1 clock whenever fractional e1 payload data is present at the rxfrtd_n pin. the local terminal equipment can latch in fractional e1 payload data at falling edge of the clock. otherwise, this pin will be a clock enable signal to receive fractional e1 output signal (rxfrtd_n) if the framer is configured accordingly. in this way, fractional e1 payload data is clocked into the terminal equipment using un-gaped receive serial output clock (rxserclk_n). a detailed discussion of the fractional e1 payload data output interface can be found in later sections. a detailed discussion of how to connect the receive payload data output interface block to the local terminal equipment with slip buffer enabled or disabled can be found in the later sections. 6.2.2.1 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is bypassed by setting the slip buffer enable [1:0] bits of the slip buffer control register to 00 or 11, the receive framer module routes the receive payload data directly to the receive payload data output interface without passing through the elastic buffer. the xrt84l38 device uses the recovered receive line clock internally to carry the receive payload data directly across the whole chip. the recovered receive line clock is essentially become timing source of the receive serial clock output. if the slip buffer is bypassed, the receive single-frame synchronization signal is automatically configured to be output signals. it should pulse high for one e1 bit period (488ns) at the last bit position of each e1 frame. by triggering on the high pulse on the receive single-frame synchronization signal, the terminal equipment can identify the end of an e1 frame and should prepare to accept payload data of the next e1 frame from the framer. the receive multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of an e1 multi-frame. by triggering on the high pulse on the receive multi-frame synchronization signal, the framer can identify the end of an e1 super-frame and should prepare to accept payload data of the next e1 super-frame from the framer. rxtsb[1] output rxsig output rxtsb[2] output rxts output r eceive f ractional e1 o utput b it = 0 r eceive f ractional e1 o utput b it = 1
xrt84l38 280 octal t1/e1/j1 framer rev. 1.0.1 see figure 81 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is bypassed and the recovered receive line clock is timing source of the receive section. the following figure 82 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal f igure 81. i nterfacing xrt84l38 to local terminal equipment with slip buffer bypassed and recov - ered receive line clock as receive timing source rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxlineclk_0 rxlineclk_7
xrt84l38 281 rev. 1.0.1 octal t1/e1/j1 framer equipment when the slip buffer is bypassed and the recovered receive line clock is timing source of the receive section. 6.2.2.2 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is enabled by setting the slip buffer enable [1:0] bits of the slip buffer control register to 01, the framer includes the two- frame elastic buffer into its data path. the receive framer module routes the receive payload data to the elastic buffer first. the receive payload data is then presented to the receive payload data output interface. the xrt84l38 device uses the recovered receive line clock internally to clock in the receive payload data into the elastic buffer. the terminal equipment should provide a 2.048mhz clock to the receive serial clock input pin to latch data out from the elastic buffer. the recovered receive line clock and the receive serial clock are generated from two different timing sources. that is, the recovered receive line clock is originating from a remote site while receive serial clock generating by a local oscillator. any mismatch in frequencies of these two clocks will result in the slip buffer to gradually fill or deplete. overtime, the elastic buffer either fills or empties completely. once that happened, a controlled slip by the xrt84l38 device will occur. the receive slip buffer slip bit of the slip buffer status register (sbsr) is set to 1. if the buffer empties and a read occurs, then a full frame of data will be repeated and the receive slip buffer empty bit of the slip buffer status register (sbsr) will be forced high. if the buffer fills and a write comes, then a full frame of data will be deleted and the receive slip buffer full bit of the slip buffer status register (sbsr) will be forced high. f igure 82. w aveforms of the s ignals c onnecting the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is b ypassed and the r ecovered l ine c lock is the t iming s ource of the r eceive s ection c rxserclk rxser rxsync(input) rxsync(output) rxchclk rxchn[4:0] rxchn[0]/rxsig rxchclk rxchn[2]/rxchn rxchn[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 282 octal t1/e1/j1 framer rev. 1.0.1 the following table demonstrates settings of the receive slip buffer slip bit, receive slip buffer empty bit and receive slip buffer full bit of the slip buffer status register. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. when the slip buffer receive synchronization direction bit is set to 0, the receive single-frame synchronization signal (rxsync_n) is an. when the slip buffer receive synchronization direction bit is set to 1,the receive single- frame synchronization signal (rxsync_n) is an input. if the receive single-frame synchronization signal is an output, it should pulse high for one e1 bit period (488ns) at the last bit position of each e1 frame. by triggering on the high pulse on the receive single-frame synchronization signal, the terminal equipment can identify the end of an e1 frame and should prepare to accept payload data of the next e1 frame from the framer. if the receive single-frame synchronization signal is an input, it should pulse high for one e1 bit period (488ns) at the first bit position (f-bit) of each e1 frame. by sampling the high pulse of the receive single- frame synchronization signal, the framer should identity the beginning of an e1 frame and can send out data in a synchronized way. it is the responsibility of the local terminal equipment to align the start of an e1 frame with the receive single-frame synchronization pulse. the receive multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of frame number one of an e1 multi-frame. by triggering on the high pulse on the receive multi- frame synchronization signal, the framer can identify the end of an e1 super-frame and should prepare to accept payload data of the next e1 super-frame from the framer. slip buffer status register (sbsr) (indirect address = 0xnah, 0x08h) b it n umber b it n ame b it t ype b it d escription 2 receive slip buffer full r/w 0 - the receive slip buffer is not full. 1 - the receive slip buffer is full and one frame of data is discarded. 1 receive slip buffer empty r/w 0 - the receive slip buffer is not empty. 1 - the receive slip buffer is empty and one frame of data is repeated. 1 receive slip buffer slip r/w 0 - the receive slip buffer does not slip. 1 - the receive slip buffer slips since either full or emptied.
xrt84l38 283 rev. 1.0.1 octal t1/e1/j1 framer see figure 83 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is enabled. f igure 83. i nterfacing xrt84l38 to local terminal equipment with slip buffer enabled or acts as fifo rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 284 octal t1/e1/j1 framer rev. 1.0.1 the following figure 84 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal equipment when the slip buffer is enabled. 6.2.2.3 connect the receive payload data output interface block to the local terminal equipment if the slip buffer is configured as fifo by setting the slip buffer enable [1:0] bits of the slip buffer control register to 10, the framer puts the elastic buffer into fifo mode. receive framer module routes the receive payload data through the first-in-first-out storage to the receive payload data output interface. the xrt84l38 device uses the recovered receive line clock internally to clock in the receive payload data into the fifo. the terminal equipment should provide an external 2.048mhz clock to the receive serial clock input pin to latch data out from the fifo. it is the responsibility of the user to phase lock the input receive serial clock to the recovered receive line clock to avoid either over-run or under-run of the fifo . the latency between writing a bit into the fifo and reading the same bit from it (read and write latency) is actually depth of the fifo, which is maintained in a programmable fashion controlled by the fifo latency register (fifolr). the largest possible depth of the fifo is thirty-two bytes or one e1 frame. the default depth of the fifo when xrt84l38 first powered up is four bytes. the table below shows the fifo latency register. in this mode, the receive single-frame synchronization signal can be either input or output depending on the settings of the slip buffer receive synchronization direction bit of the slip buffer control register. when the slip buffer receive synchronization direction bit is set to 0, the receive single-frame synchronization signal (rxsync_n) is an. when the slip buffer receive synchronization direction bit is set to 1,the receive single- frame synchronization signal (rxsync_n) is an input. f igure 84. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is e nabled fifo latency register (fifol) (indirect address = 0xn0h, 0x17h) b it n umber b it n ame b it t ype b it d escription 4-0 fifo latency r/w these bits determine depth of the fifo in terms of bytes. the largest possible value is thirty-two bytes or one e1 frame. c rxserclk rxser rxsync(input) rxsync(output) rxchclk rxchn[4:0] rxchn[0]/rxsig rxchclk rxchn[2]/rxchn rxchn[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 285 rev. 1.0.1 octal t1/e1/j1 framer if the receive single-frame synchronization signal is an output, it should pulse high for one e1 bit period (488ns) at the last bit position of each e1 frame. by triggering on the high pulse on the receive single-frame synchronization signal, the terminal equipment can identify the end of an e1 frame and should prepare to accept payload data of the next e1 frame from the framer. if the receive single-frame synchronization signal is an input, it should pulse high for one e1 bit period (488ns) at the first bit position (f-bit) of each e1 frame. by sampling the high pulse of the receive single- frame synchronization signal, the framer should identity the beginning of an e1 frame and can send out data in a synchronized way. it is the responsibility of the local terminal equipment to align the start of an e1 frame with the receive single-frame synchronization pulse. the receive multi-frame synchronization signal should pulse high for one e1 bit period (488ns) at the last bit position of frame number one of an e1 multi-frame. by triggering on the high pulse on the receive multi- frame synchronization signal, the framer can identify the end of an e1 super-frame and should prepare to accept payload data of the next e1 super-frame from the framer. see figure 85 for how to connect the receive payload data output interface block to the local terminal equipment when the slip buffer is acted as fifo. f igure 85. i nterfacing xrt84l38 to local terminal equipment with slip buffer enabled or acts as fifo rxserclk_0 rxser_0 rxmsync_0 rxsync_0 rxtsclk_0 rxtsb[4:0]_0 rxserclk_7 rxser_7 rxmsync_7 rxsync_7 rxtsclk_7 rxtsb[4:0]_7 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38
xrt84l38 286 octal t1/e1/j1 framer rev. 1.0.1 the following figure 86 shows waveforms of the signals (rxserclk_n, rxser_n, rxsync_n, rxtsclk_n and rxtsb[4:0]_n) which connecting the receive payload data output interface block to the local terminal equipment when the slip buffer is acted as fifo. 6.2.3 high speed receive back-plane interface the high-speed back-plane interface supports payload data to be taken from or presented to the local terminal equipment at different data rates. in e1 mode, supported high-speed data rates are mvip 2.048mbit/ s, 4.096mbit/s, 8.192mbit/s, multiplexed 16.384mbit/s, hmvip 16.384mbit/s or h.100 16.384mbit/s. the receive multiplex enable bit and the receive interface mode select [1:0] bits of the receive interface control register (ricr) determine the receive back-plane interface data rate. the following table shows configurations of the receive multiplex enable bit and the receive interface mode select [1:0] bits of the receive interface control register (ricr). f igure 86. w aveforms of the s ignals that c onnect the r eceive p ayload d ata o utput i nterface block to the local t erminal e quipment when the s lip b uffer is acted as fifo receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 2 receive multi - plex enable r/w 0 - the receive back-plane interface block is configured to non-channel-multi - plexed mode 1 - the receive back-plane interface block is configured to channel-multiplexed mode 1-0 receive inter - face mode select r/w when combined with the receive multiplex enable bit, these bits determine the receive back-plane interface data rate. c rxserclk rxser rxsync(input) rxsync(output) rxchclk rxchn[4:0] rxchn[0]/rxsig rxchclk rxchn[2]/rxchn rxchn[1]/rxfrtd c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 a b d c a b d c a b d c a b d input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 timeslot #0 timeslot #5 timeslot #6 timeslot #16
xrt84l38 287 rev. 1.0.1 octal t1/e1/j1 framer the table below shows the combinations of receive multiplex enable bit and receive interface mode select [1:0] bits and the resulting receive back-plane interface data rates. when the receive multiplex enable bit is set to zero, the framer is configured in non-channel-multiplexed mode. the possible data rates are xrt84v24 compatible 2.048mbit/s, mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s. in non-channel-multiplexed mode, payload data of each channel are sending out from the receive high-speed back-plane interface separately. each channel uses its own receive serial clock, receive serial data, receive single-frame synchronization signal and receive multi-frame synchronization signal as interface between the framer and the terminal equipment. section 2.1.1.1, 2.1.1.2 and 2.1.1.3 provide details on how to connect the receive payload data interface block with the local terminal equipment when the back-plane interface data rate is 2.048mbit/s. when the back-plane interface data rate is mvip 2.048mbit/s, 4.096mbit/s and 8.192mbit/s, the receive serial clock, receive serial data and receive single-frame synchronization are all configured as inputs. the receive multi-frame synchronization signal is still output. the receive serial clock is configured as an input timing source for the high-speed back-plane interface with frequencies of 2.048 mhz, 4.096 mhz and 8.192 mhz respectively. the table below summaries the clock frequencies of rxserclk_n input when the framer is operating in non- multiplexed high-speed back-plane mode. when the receive multiplex enable bit is set to one, the framer is configured in channel-multiplexed mode. the possible data rates are bit-multiplexed 16.384mbit/s, hmvip 16.384mbit/s and h.100 16.384mbit/s. in channel-multiplexed mode, four channels share the receive serial data, receive single-frame synchronization signal and receive serial clock of one channel as interface between the framer and the terminal equipment. the receive serial clock runs at frequencies of 12.352 mhz or 16.384 mhz. it serves as the primary clock source for the high-speed back-plane interface. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. the receive single-frame synchronization signal of channel 0 pulses high at the beginning of the frame with data r eceive m ultiplex e nable b it r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate 0 0 0 xrt84v24 compatible 2.048mbit/s 0 0 1 mvip 2.048mbit/s 0 1 0 4.096mbit/s 0 1 1 8.192mbit/s 1 0 0 - 1 0 1 bit multiplexed 16.384mbit/s 1 1 0 hmvip 16.384mbit/s 1 1 1 h.100 16.384mbit/s receive multiplex enable bit = 0 r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate r x s er c lk 0 0 xrt84v24 compatible 2.048mbit/s 2.048mhz 0 1 mvip 2.048mbit/s 2.048 mhz 1 0 4.096mbit/s 4.096 mhz 1 1 8.192mbit/s 8.192 mhz
xrt84l38 288 octal t1/e1/j1 framer rev. 1.0.1 from channel 0-3 multiplexed together. the receive single-frame synchronization signal of channel 4 pulses high at the beginning of the frame with data from channel 4-7 multiplexed together. the table below summaries the clock frequencies of rxserclk_n input when the framer is operating in multiplexed high-speed back-plane mode. when the frame is running at high-speed back-plane interface mode other than the 2.048mbit/s data rate, the receive single-frame synchronization signal could pulse high or low indicating boundaries of e1 frames. the receive synchronization pulse low bit of the receive interface control register (ticr) determines whether the receive single-frame synchronization signal is high active or low active. the table below shows configurations of the receive synchronization pulse low bit of the receive interface control register (ricr). throughout the discussion of this datasheet, we assume that the receive single-frame synchronization signal pulses high unless stated otherwise. the following sections discuss details of how to operate the framer in different back-plane interface speed mode and how to connect the receive payload data output interface block to the local terminal equipment. 6.2.3.1 e1 receive input interface - mvip 2.048 mhz when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 01, the receive back-plane interface of framer is running at a data rate of 2.048mbit/s. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 2.048mhz clock to the receive serial receive multiplex enable bit = 1 r eceive i nterface m ode s elect b it 1 r eceive i nterface m ode s elect b it 0 b ack - plane i nterface d ata r ate r x s er c lk 0 0 - - 0 1 bit-multiplexed 16.384mbit/s 16.384 mhz 1 0 hmvip 16.384mbit/s 16.384 mhz 1 1 h.100 16.384mbit/s 16.384 mhz receive interface control register (ricr) (indirect address = 0xn0h, 0x22h) b it n umber b it n ame b it t ype b it d escription 3 receive syn - chronization pulse low r/w 0 - the receive single-frame synchronization signal will pulse high indicating the beginning of an e1 frame when the high-speed back-plane interface is run - ning at a mode other than the 2.048mbit/s. 1 - the receive single-frame synchronization signal will pulse low indicating the beginning of an e1 frame when the high-speed back-plane interface is run - ning at a mode other than the 2.048mbit/s.
xrt84l38 289 rev. 1.0.1 octal t1/e1/j1 framer clock input. the receive high-speed back-plane interface of the framer then sends out serial data at rising edge of the receive serial clock. the local terminal equipment samples the serial data at falling edge of the clock. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of an e1 frame and start pumping payload data out. see figure 87 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in mvip 2.048mbit/s mode. the timing diagram of input signals to the framer when running at mvip 2.048mbit/s mode is shown in figure 88 . f igure 87. i nterfacing xrt84l38 to local terminal equipment using mvip 2.048m bit / s data bus f igure 88. t iming d iagram of i nput signals to the f ramer when running at mvip 2.048m bit / s rxserclk_0 (2.048mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (2.048mhz) rxser_7 rxmsync rxsync_7 rxserclk rxserclk(inv) rxser rxsync(input) rxsync(input) (mvip) rxchn[0]/rxsig rxchn[1]/frrxd rxchclk (rxsyncfrtd=1) rxchclk(inv) rxchclk (rxsyncfrtd=1) timeslot 2 f timeslot 3 timeslot 4 timeslot 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d c a b d c a b d c a b d c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 c1 c2 c3 c4 c5 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 rxchn[2]/rxchn
xrt84l38 290 octal t1/e1/j1 framer rev. 1.0.1 6.2.3.2 e1 receive input interface - 4.096 mhz (this interface mode is the same as running at 2.048 mhz. the only difference is that the receive serial clock runs two times faster at 4.096 mhz) when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 10, the receive back-plane interface of framer is running at a clock rate of 4.096mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 4.096mhz clock to the receive serial clock input. the receive high-speed back-plane interface of the framer then sends out serial data at every other rising edge of the receive serial clock. the local terminal equipment samples the serial data at every other falling edge of the clock. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of an e1 frame and start pumping payload data out. see figure 89 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in 4.096mbit/s mode. f igure 89. i nterfacing xrt84l38 to local terminal equipment using 4.096m bit / s data bus rxserclk_0 (4.096mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (4.096mhz) rxser_7 rxmsync rxsync_7
xrt84l38 291 rev. 1.0.1 octal t1/e1/j1 framer the timing diagram of input signals to the framer when running at 4.096mbit/s mode is shown in figure 90 . 6.2.3.3 e1 receive input interface - 8.192 mhz (this interface mode is the same as running at 2.048 mhz. the only difference is that the receive serial clock runs four times faster at 8.192mhz) when the receive multiplex enable bit is set to zero and the receive interface mode select [1:0] bits are set to 11, the receive back-plane interface of framer is running at a clock rate of 8.192mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_n at an e1 equivalent data rate of 2.048mbit/s. the local terminal equipment supplies a free-running 8.192mhz clock to the receive serial clock input. the receive high-speed back-plane interface of the framer then sends out serial data at every other four rising edge of the receive serial clock. the local terminal equipment samples the serial data at every other four falling edge of the clock. the receive single-frame synchronization input signal (rxsync_n) should pulse high at the beginning of the 256-bit frame indicating start of the frame. by sampling the high pulse of the receive single-frame synchronization signal, the framer can identity the beginning of an e1 frame and start pumping payload data out. f igure 90. t iming d iagram of input signals to the framer when running at 4.096m bit / s mode txserclk (2mhz) txserclk (inv) txser txsync(input) txchclk(inv) txchn[0]/txsig txchn[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 txserclk (4mhz) don't care don't care
xrt84l38 292 octal t1/e1/j1 framer rev. 1.0.1 see figure 91 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in 8.192mbit/s mode. the timing diagram of input signals to the framer when running at 8.192mbit/s mode is shown in figure 92 . 6.2.3.4 e1 receive input interface - bit-multiplexed 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 01, the receive back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) f igure 91. i nterfacing xrt84l38 to local terminal equipment using 8.192m bit / s data bus f igure 92. t iming diagram of input signals to the framer when running at 8.192m bit / s mode rxserclk_0 (8.192mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0 receive payload data input interface chn 7 terminal equipment xrt84l38 rxserclk_7 (8.192mhz) rxser_7 rxmsync_7 rxsync_7 t xserclk (2mhz) t xserclk (inv) t xser t xsync(input) t xchclk(inv) t xchn[0]/txsig t xchn[1]/txfrtd f 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 c a b d don't care c a b d don't care c a b d don't care don't care c a b d don't care note: the following signals are not aligned with the signals shown above. the txchclk is derived from 1.544mhz transmit clock. don't care 8 7 6 5 4 3 2 1 don't care 8 7 6 5 4 3 2 1 t xserclk (8mhz) don't care don't care
xrt84l38 293 rev. 1.0.1 octal t1/e1/j1 framer ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. it multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a bit-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the first payload bit of timeslot 0 of channel 1 and 2. the first payload bit of timeslot 0 of channel 3 is sent last. after the first bits of timeslot 0 of all four channels are sent, it comes the second bit of timeslot 0 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y 2. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 1 1 1 1 1 2 1 2 1 3 1 3 second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 2 0 2 0 2 1 2 1 2 2 2 2 2 3 2 3
xrt84l38 294 octal t1/e1/j1 framer rev. 1.0.1 the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 3. after the first octets of all four channels are sent, the receive high-speed back-plane interface will start sending the second octets following the same rules of step 1 and 2. the receive single-frame synchronization signal of chann el 0 pulses high for one clock cycle at the first bit position of the data stream with data from channel 0-3 multiplexed together. the receive single-frame synchronization signal of channel 4 pulses high for one clock cycle at the first bit position of the data stream with data from channel 4-7 multiplexed together. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 6 0 b 0 6 1 b 1 6 2 b 2 6 3 b 3 seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 7 0 c 0 7 1 c 1 7 2 c 2 7 3 c 3 eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 8 0 d 0 8 1 d 1 8 2 d 2 8 3 d 3
xrt84l38 295 rev. 1.0.1 octal t1/e1/j1 framer see figure 93 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in bit-multiplexed 16.384mbit/s mode. the input signal timing is shown in figure 94 below when the framer is running at bit-multiplexed 16.384mbit/ s mode. 6.2.3.5 e1 receive input interface - hmvip 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 10, the receive back-plane interface of framer is running at a clock rate of 16.384mhz. the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. the receive high-speed back-plane interface multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin f igure 93. i nterfacing xrt84l38 to local terminal equipment using 16.384 m bit / s data bus f igure 94. t iming signal when the framer is running at b it -m ultiplexed 16.384m bit / s mode rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (16.384mhz) rxserclk (inv) rxser rxsync(input) f 0 f 0 f 1 f 1 f 2 f 2 f 3 f 3 1 0 x 1 1 x x x 1 2 1 3 2 0 x 2 1 x x 3 0 4 0 x 5 0 a 0 5 1 a 1 5 2 a 2 5 3 a 3 56 cycles
xrt84l38 296 octal t1/e1/j1 framer rev. 1.0.1 of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the terminal equipment will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y 2. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 third octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3
xrt84l38 297 rev. 1.0.1 octal t1/e1/j1 framer payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 3. after the first octets of all four channels are sent, the receive high-speed back-plane interface will start sending the second octets following the same rules of step 1 and 2. the receive single-frame synchronization signal should pulse high for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0- 3. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 fourth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 298 octal t1/e1/j1 framer rev. 1.0.1 see figure 95 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in hmvip 16.384mbit/s mode. the input signal timing is shown in figure 96 below when the framer is running at hmvip 16.384mbit/s mode. 6.2.3.6 e1 receive input interface - h.100 16.384mbit/s when the receive multiplex enable bit is set to one and the receive interface mode select [1:0] bits are set to 11, the receive back-plane interface of framer is running at h.100 16.384mbit/s mode. (the hmvip mode and the h.100 mode are essential the same except for the high pulse position of the receive single-frame synchronization signal) the interface consists of the following pins: ? data input (rxser_n) ? receive serial clock input signal (rxserclk_n) ? receive single-frame synchronization input signal (rxsync_n) ? receive input clock (rxinclk_n) ? receive time-slot indication clock (rxtsclk_n) f igure 95. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus f igure 96. t iming s ignal when the framer is running at hmvip 16.384m bit / s mode rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (16.384mhz) rxserclk (inv) rxser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 rxsig rxsync(input) hmvip, negative sync rxsync(input) hmvip, positive sync start of frame x y : x is the bit number and y is the channel number
xrt84l38 299 rev. 1.0.1 octal t1/e1/j1 framer ? receive time slot indicator bits (rxtsb[4:0]_n) the receive back-plane interface is pumping out data through rxser_0 or rxser_4 pins at 16.384mbit/s. the receive high-speed back-plane interface multiplexes payload and signaling data of every four channels into one data stream. payload and signaling data of channel 0-3 are multiplexed onto the receive serial data pin of channel 0. payload and signaling data of channel 4-7 are multiplexed onto the receive serial data pin of channel 4. free-running clocks of 16.384mhz are supplied to the receive serial clock pin of channel 0 and channel 4 of the framer. the receive high-speed back-plane interface of the farmer provides data at rising edge of this receive serial clock. the local terminal equipment then latches incoming serial data at falling edge of the clock. the receive high-speed back-plane interface maps four 2.048mbit/s e1 data streams into this 16.384mbit/s data stream as described below: 1. payload data of four channels are repeated and grouped together in a byte-interleaved way. the first pay - load bit of timeslot 0 of channel 0 is sent first, followed by the second payload bit of timeslot 0 of channel 0 and so on. after all the bits of timeslot 0 of channel 0 is sent repeatedly, the receive high-speed back- plane interface will start sending the payload bits of timeslot 0 of channel 1 and 2. the payload bits of timeslot 0 of channel 3 are sent the last. after the payload bits of timeslot 0 of all four channels are sent, it comes the payload bits of timeslot 1 of channel 0 and so on. the table below demonstrates how payload bits of four channels are mapped into the 16.384mbit/s data stream. x y : the xth payload bit of channel y first octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 third octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 1 1 1 2 1 2 1 3 1 3 1 4 1 4 1 fifth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 2 1 2 2 2 2 2 3 2 3 2 4 2 4 2 seventh octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 1 3 1 3 2 3 2 3 3 3 3 3 4 3 4 3
xrt84l38 300 octal t1/e1/j1 framer rev. 1.0.1 2. the receive high-speed back-plane interface also multiplexed signaling bits with payload bits and sent them together through the 16.384mbit/s data stream. when the receive high-speed back-plane interface is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit a of that particular channel. similarly, the sixth payload bit of a particular channels is followed by the signaling bit b of that channel; the seventh payload bit is followed by the signaling bit c; the eighth payload bit is followed by the signaling bit d. the following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384mbit/s data stream. x y : the xth payload bit of channel y a y : the signaling bit a of channel y 3. after the first octets of all four channels are sent, the receive high-speed back-plane interface will start sending the second octets following the same rules of step 1 and 2. the receive single-frame synchronization signal should pulse high for two clock cycles (the last bit position of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0-3. the receive single-frame synchronization signal of channel 0 pulses high to identify the start of multiplexed data stream of channel 0- 3. by sampling the high pulse of the receive single-frame synchronization signal, the receive high-speed back-plane interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of that frame. second octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 0 a 0 6 0 b 0 7 0 c 0 8 0 d 0 fourth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 1 a 1 6 1 b 1 7 1 c 1 8 1 d 1 sixth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 2 a 2 6 2 b 2 7 2 c 2 8 2 d 2 eighth octet of 16.384mbit/s data stream b it 0 b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 5 3 a 3 6 3 b 3 7 3 c 3 8 3 d 3
xrt84l38 301 rev. 1.0.1 octal t1/e1/j1 framer see figure 97 below for how to interface the local terminal equipment with the receive payload data output interface block of the framer in hmvip 16.384mbit/s mode. the input signal timing is shown in figure 98 below when the framer is running at h.100 16.384mbit/s mode. f igure 97. i nterfacing xrt84l38 to local terminal equipment using 16.384m bit / s data bus f igure 98. t iming s ignal when the framer is running at h.100 16.384m bit / s mode rxserclk_0 (16.384mhz) rxser_0 rxmsync_0 rxsync_0 receive payload data input interface chn 0-3 receive payload data input interface chn 4 terminal equipment xrt84l38 rxserclk_4 (16.384mhz) rxser_4 rxmsync_4 rxsync_4 rxserclk (16.384mhz) rxserclk (inv) rxser 1 2 1 2 5 2 5 2 1 0 1 0 2 0 2 0 3 0 4 0 3 0 4 0 5 0 a 0 6 0 b 0 7 3 7 3 8 3 8 3 f 0 f 1 f 0 f 1 f 2 f 2 f 3 f 3 56 cycles 5 3 5 3 6 3 6 3 7 3 7 3 8 3 8 3 0 0 a 2 a 2 0 0 0 0 0 a 0 0 a 0 b 0 b 0 c 0 c 0 c 3 c 3 d 3 d 3 1 1 1 1 1 1 1 1 56 cycles a 3 a 3 b 3 b 3 c 3 c 3 d 3 d 3 rxsig start of frame x y : x is the bit number and y is the channel number rxsync(input) h.100, negative sync rxsync(input) h.100, positive sync delayer h.100 rxsync(input) h.100, negative sync rxsync(input) h.100, positive sync
xrt84l38 302 octal t1/e1/j1 framer rev. 1.0.1 7.0 ds1 overhead interface block the xrt84l38 has the ability to extract or insert ds1 data link information from or into the following: ? facility data link (fdl) bits in esf framing format mode ? signaling framing (fs) bits in slc?96 and n framing format mode ? remote signaling (r) bits in t1dm framing format mode the source and destination of these inserted and extracted data link bits would be from either the internal hdlc controller or the external device accessible through ds1 overhead interface block. the operation of the transmit overhead input interface block and the receive overhead output interface block will be discussed separately. 7.1 ds1 transmit overhead input interface block 7.1.1 description of the ds1 transmit overhead input interface block the ds1 transmit overhead input interface block will allow an external device to be the provider of the facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in the slc96 and n framing format mode and remote signaling (r) bit in t1dm framing format mode. this interface provides interface signals and required interface timing to shift in proper data link information at proper time. the transmit overhead input interface for a given framer consists of two signals. ? txohclk_n: the transmit overhead input interface clock output signal ? txoh_n: the transmit overhead input interface input signal. the transmit overhead input interface clock output pin (txohclk_n) generates a rising clock edge for each data link bit position according to configuration of the framer. the data link equipment interfaced to the transmit overhead input interface block should update the data link bits on the txoh_n line upon detection of the rising edge of txohclk_n. the transmit overhead input interface block will sample and latch the data link bits on the txoh_n line on the falling edge of txohclk_n. the data link bits will be included and transmitted via the outgoing ds1 frames. the figure below shows block diagram of the ds1 transmit overhead input interface of xrt84l38. 7.1.2 configure the ds1 transmit overhead input interface module as source of the facility data link (fdl) bits in esf framing format mode the fdl bits in esf framing format mode can be inserted from: ? ds1 transmit overhead input interface block ? ds1 transmit hdlc controller ? ds1 transmit serial input interface. f igure 99. b lock d iagram of the ds1 t ransmit o verhead i nput i nterface of the xrt84l38 transmit overhead input interface txoh_n txohclk_n to transmit framer block
xrt84l38 303 rev. 1.0.1 octal t1/e1/j1 framer the transmit data link source select bits of the transmit data link select register (tdlsr) controls the insertion of data link bits into the fdl bits in esf framing format mode. the table below shows configuration of the transmit data link source select bits of the transmit data link select register (tdlsr). if the transmit data link source select bits of the transmit data link select register are set to 10, the transmit overhead input interface block becomes input source of the fdl bits. the xrt84l38 allows the user to select bandwidth of the facility data link channel in esf framing format mode. the fdl can be either a 4khz or 2khz data link channel. the transmit data link bandwidth select bits of the transmit data link select register (tdlsr) determine the bandwidth of fdl channel in esf framing format mode. the table below shows configuration of the transmit data link bandwidth select bits of the transmit data link select register (tdlsr).) figure 100 below shows the timing diagram of the input and output signals associated with the ds1 transmit overhead input interface module in esf framing format mode. transmit data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 transmit data link source select r/w 00 - the facility data link bits are inserted into the framer through either the lapd controller or the slca96 buffer. 01 - the facility data link bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 10 - the facility data link bits are inserted into the framer through the transmit overhead input interface via the txoh_n pins. 11 - the facility data link bits are forced to one by the framer. transmit data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 5-4 transmit data link bandwidth select r/w 00 - the facility data link is a 4khz channel. all available fdl bits (first bit of every other frame) are used as data link bits. 01 - the facility data link is a 2khz channel. only the odd fdl bits (first bit of frame 1, 5, 9?) are used as data link bits. 10 - the facility data link is a 2khz channel. only the even fdl bits (first bit of frame 3, 7, 11?) are used as data link bits. f igure 100. ds1 t ransmit o verhead i nput i nterface t iming in esf f raming f ormat mode 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # txsync txohclk (4khz) txoh (4khz) txohclk (2khz, odd) txoh (2khz, odd) txohclk (2khz, even) txoh (2khz, even)
xrt84l38 304 octal t1/e1/j1 framer rev. 1.0.1 7.1.3 configure the ds1 transmit overhead input interface module as source of the signaling framing (fs) bits in n or slc?96 framing format mode the fs bits in slc?96 and n framing format mode can be inserted from: ? ds1 transmit overhead input interface block ? ds1 transmit hdlc controller ? ds1 transmit serial input interface. the transmit data link source select bits of the transmit data link select register (tdlsr) controls the insertion of data link bits into the fs bits in n or slc?96 framing format mode. the table below shows configuration of the transmit data link source select bits of the transmit data link select register (tdlsr). if the transmit data link source select bits of the transmit data link select register are set to 10, the transmit overhead input interface block becomes input source of the fs bits. figure 101 below shows the timing diagram of the input and output signals associated with the ds1 transmit overhead input interface module in n or slc?96 framing format mode. 7.1.4 configure the ds1 transmit overhead input interface module as source of the remote signaling (r) bits in t1dm framing format mode the r bits in t1dm framing format mode can be inserted from: ? ds1 transmit overhead input interface block ? ds1 transmit hdlc controller ? ds1 transmit serial input interface. transmit data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 transmit data link source select r/w 00 - the signaling framing bits are inserted into the framer through either the lapd controller or the slca96 buffer. 01 - the signaling framing bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 10 - the signaling framing bits are inserted into the framer through the transmit overhead input interface via the txoh_n pins. 11 - the signaling framing bits are forced to one by the framer. f igure 101. ds1 t ransmit o verhead i nput t iming in n or slc?96 f raming f ormat m ode txohclk (4khz) txoh (4khz) 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # txsync
xrt84l38 305 rev. 1.0.1 octal t1/e1/j1 framer the transmit data link source select bits of the transmit data link select register (tdlsr) controls the insertion of data link bits into the r bits in t1dm framing format mode. the table below shows configuration of the transmit data link source select bits of the transmit data link select register (tdlsr). if the transmit data link source select bits of the transmit data link select register are set to 10, the transmit overhead input interface block becomes input source of the r bits. since r bit presents in timeslot 24 of every t1dm frame, therefore, bandwidth of t1dm data link channel is 8khz. figure 102 below shows the timing diagram of the input and output signals associated with the ds1 transmit overhead input interface module in t1dm framing format mode. transmit data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 transmit data link source select r/w 00 - the remote signaling bits are inserted into the framer through either the lapd controller or the slca96 buffer. 01 - the remote signaling bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 10 - the remote signaling bits are inserted into the framer through the transmit overhead input interface via the txoh_n pins. 11 - the remote signaling bits are forced to one by the framer. f igure 102. ds1 t ransmit o verhead i nput i nterface module in t1dm f raming f ormat mode txohclk (t1dm) 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # txsync
xrt84l38 306 octal t1/e1/j1 framer rev. 1.0.1 7.2 ds1 receive overhead output interface block 7.2.1 description of the ds1 receive overhead output interface block the ds1 receive overhead output interface block allows an external device to be the consumer of the facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in the slc96 and n framing format mode and remote signaling (r) bit in t1dm framing format mode this interface provides interface signals and required interface timing to shift out proper data link information at proper time. the receive overhead output interface for a given framer consists of two signals. ? rxohclk_n: the receive overhead output interface clock output signal ? rxoh_n: the receive overhead output interface output signal. the receive overhead output interface clock output pin (rxohclk_n) generates a rising clock edge for each data link bit position according to configuration of the framer. the data link bits extracted from the incoming t1 frames are outputted from the receive overhead output interface output pin (rxoh_n) at the rising edge of rxohclk_n. the data link equipment should sample and latch the data link bits at the falling edge of rxohclk_n. the figure below shows block diagram of the receive overhead output interface of xrt84l38. 7.2.2 configure the ds1 receive overhead output interface module as destination of the facility data link (fdl) bits in esf framing format mode the fdl bits in esf framing format mode can be extracted to: ? ds1 receive overhead output interface block ? ds1 receive hdlc controller ? ds1 receive serial output interface. the receive data link source select bits of the receive data link select register (rdlsr) controls the extraction of fdl bits in esf framing format mode. the table below shows configuration of the receive data link source select bits of the receive data link select register (rdlsr). f igure 103. b lock d iagram of the ds1 r eceive o verhead o utput i nterface of xrt84l38 receive overhead output interface rxoh_n rxohclk_n from receive framer block
xrt84l38 307 rev. 1.0.1 octal t1/e1/j1 framer if the receive data link source select bits of the receive data link select register are set to 10, the receive overhead output interface block becomes output source of the fdl bits. the xrt84l38 allows the user to select bandwidth of the facility data link channel in esf framing format mode. the fdl can be either a 4khz or 2khz data link channel. the receive data link bandwidth select bits of the receive data link select register (rdlsr) determine the bandwidth of fdl channel in esf framing format mode. the table below shows configuration of the receive data link bandwidth select bits of the receive data link select register (tdlsr). figure 104 below shows the timing diagram of the output and output signals associated with the ds1 receive overhead output interface module in esf framing format mode. receive data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 receive data link destination select r/w 00 - the extracted facility data link bits are stored in either the lapd con - troller or the slca96 buffer. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 01 - the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 10 - the extracted facility data link bits are outputted from the framer through the receive overhead output interface via the rxoh_n pins. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 11 - the facility data link bits are forced to one by the framer. receive data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 5-4 receive data link bandwidth select r/w 00 - the facility data link is a 4khz channel. all available fdl bits (first bit of every other frame) are used as data link bits. 01 - the facility data link is a 2khz channel. only the odd fdl bits (first bit of frame 1, 5, 9?) are used as data link bits. 10 - the facility data link is a 2khz channel. only the even fdl bits (first bit of frame 3, 7, 11?) are used as data link bits.
xrt84l38 308 octal t1/e1/j1 framer rev. 1.0.1 7.2.3 configure the ds1 receive overhead output interface module as destination of the signaling framing (fs) bits in n or slc?96 framing format mode the fs bits in slc?96 and n framing format mode can be extracted to: ? ds1 receive overhead output interface block ? ds1 receive hdlc controller ? ds1 receive serial output interface. the receive data link source select bits of the receive data link select register (rdlsr) controls the destination of fs bits in n or slc?96 framing format mode. the table below shows configuration of the receive data link source select bits of the receive data link select register (rdlsr). if the receive data link source select bits of the receive data link select register are set to 10, the receive overhead output interface block outputs fs bits extracted from the incoming t1 data stream. f igure 104. ds1 r eceive o verhead o utput i nterface module in esf framing format mode receive data link select register (tdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 receive data link source select r/w 00 - the extracted facility data link bits are stored in either the lapd con - troller or the slca96 buffer. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 01 - the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 10 - the extracted facility data link bits are outputted from the framer through the receive overhead output interface via the rxoh_n pins. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 11 - the facility data link bits are forced to one by the framer. 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # rxsync rxohclk (4khz) rxoh (4khz) rxohclk (2khz, odd) rxoh (2khz, odd) rxohclk (2khz, even) rxoh (2khz, even)
xrt84l38 309 rev. 1.0.1 octal t1/e1/j1 framer figure 105 below shows the timing diagram of the output signals associated with the ds1 receive overhead output interface module in n or slc?96 framing format mode. 7.2.4 configure the ds1 receive overhead output interface module as destination of the remote signaling (r) bits in t1dm framing format mode the r bits in t1dm framing format mode can be extracted to: ? ds1 receive overhead output interface block ? ds1 receive hdlc controller ? ds1 receive serial output interface. the receive data link source select bits of the receive data link select register (rdlsr) controls the destination of r bits in t1dm framing format mode. the table below shows configuration of the receive data link source select bits of the receive data link select register (rdlsr). if the receive data link source select bits of the receive data link select register are set to 10, the receive overhead output interface block outputs the r bits extracted from the incoming t1 data stream. since r bit presents in timeslot 24 of every t1dm frame, therefore, bandwidth of t1dm data link channel is 8khz. f igure 105. ds1 r eceive o verhead o utput i nterface t iming in n or slc?96 f raming f ormat mode receive data link select register (rdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 receive data link source select r/w 00 - the extracted facility data link bits are stored in either the lapd con - troller or the slc ? 96 buffer. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 01 - the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 10 - the extracted facility data link bits are outputted from the framer through the receive overhead output interface via the rxoh_n pins. at the same time, the extracted facility data link bits are outputted from the framer through the receive serial data output interface via the rxser_n pins. 11 - the facility data link bits are forced to one by the framer. 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # rxsync rxohclk (4khz) rxoh (4khz)
xrt84l38 310 octal t1/e1/j1 framer rev. 1.0.1 figure 106 below shows the timing diagram of the output signals associated with the ds1 receive overhead output interface module in t1dm framing format mode. f igure 106. ds1 r eceive o verhead o utput i nterface t iming in t1dm f raming f ormat mode 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # rxsync rxohclk (4khz) rxoh (4khz) rxohclk (2khz, odd) rxoh (2khz, odd) rxohclk (2khz, even) rxoh (2khz, even)
xrt84l38 311 rev. 1.0.1 octal t1/e1/j1 framer 8.0 e1 overhead interface block the xrt84l38 has the ability to extract or insert e1 data link information from or into the e1 national bit sequence. the source and destination of these inserted and extracted data link bits would be from either the internal hdlc controller or the external device accessible through e1 overhead interface block. the operation of the transmit overhead input interface block and the receive overhead output interface block will be discussed separately. 8.1 e1 transmit overhead input interface block 8.1.1 description of the e1 transmit overhead input interface block the e1 transmit overhead input interface block will allow an external device to be the provider of the e1 national bit sequence. this interface provides interface signals and required interface timing to shift in proper data link information at proper time. the transmit overhead input interface for a given framer consists of two signals. ? txohclk_n: the transmit overhead input interface clock output signal ? txoh_n: the transmit overhead input interface input signal. the transmit overhead input interface clock output pin (txohclk_n) generates a rising clock edge for each national bit that is configured to carry data link information according to setting of the framer. the data link equipment interfaced to the transmit overhead input interface should update the data link bits on the txoh_n line upon detection of the rising edge of txohclk_n. the transmit overhead input interface block will sample and latch the data link bits on the txoh_n line on the falling edge of txohclk_n. the data link bits will be included in and transmitted via the outgoing e1 frames. the figure below shows block diagram of the ds1 transmit overhead input interface of xrt84l38. 8.1.2 configure the e1 transmit overhead input interface module as source of the national bit sequence in e1 framing format mode the national bit sequence in e1 framing format mode can be inserted from: ? e1 transmit overhead input interface block ? e1 transmit hdlc controller ? e1 transmit serial input interface the purpose of the transmit overhead input interface is to permit data link equipment direct access to the sa4 through sa8 national bits that are to be transported via the outbound frames. the transmit data link source select [1:0] bits, within the synchronization mux register (smr) determine source of the sa4 through sa8 national bits to be inserted into the outgoing e1 frames. f igure 107. b lock d iagram of the e1 t ransmit o verhead i nput i nterface of xrt84l38 transmit overhead input interface txoh_n txohclk_n to transmit framer block
xrt84l38 312 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configuration of the transmit data link source select [1:0] bits of the synchronization mux register (smr). if the transmit data link source select bits of the transmit data link select register are set to 10, the transmit overhead input interface block becomes input source of the fdl bits. the xrt84l38 allows the user to decide on the following: ? how many of the national bits will be used to carry the data link information bits ? which of these national bits will be used to carry the data link information bits. the transmit sa data link select bits of the transmit signaling and data link select register (tsdlsr) determine which ones of the national bits are configured as data link bits in e1 framing format mode. depending upon the configuration of the transmit signaling and data link select register, either of the following cases may exists: ? none of the national bits are used to transport the data link information bits (that is, data link channel of xrt84l38 is inactive). ? any combination of between 1 and all 5 of the national bits can be selected to transport the data link information bits. the table below shows configuration of the transmit sa data link select bits of the transmit signaling and data link select register (tsdlsr). for every sa bit that is selected to carry data link information, the transmit overhead input interface will supply a clock pulse, via the txohclk_n output pin, such that: synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 3-2 transmit data link source select [1:0] r/w 00 - the sa4 through sa8 national bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 01 - the sa4 through sa8 national bits are inserted into the framer through the transmit lapd controller. 10 - the sa4 through sa8 national bits are inserted into the framer through the transmit overhead input interface via the txoh_n pins. 11 - the sa4 through sa8 national bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. transmit signaling and data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 7 transmit sa8 data link select r/w 0 - source of the sa8 nation bit is not from the data link interface. 1 - source the sa8 national bit from the data link interface. 6 transmit sa7 data link select r/w 0 - source of the sa7 nation bit is not from the data link interface. 1 - source the sa7 national bit from the data link interface. 5 transmit sa6 data link select r/w 0 - source of the sa6 nation bit is not from the data link interface. 1 - source the sa6 national bit from the data link interface. 4 transmit sa5 data link select r/w 0 - source of the sa5 nation bit is not from the data link interface. 1 - source the sa5 national bit from the data link interface. 3 transmit sa4 data link select r/w 0 - source of the sa4 nation bit is not from the data link interface. 1 - source the sa4 national bit from the data link interface.
xrt84l38 313 rev. 1.0.1 octal t1/e1/j1 framer ? the data link equipment interfaced to the transmit overhead input interface should update the data on the txoh_n line upon detection of the rising edge of txohclk_n. ? the transmit overhead input interface will sample and latch the data on the txoh_n line on the falling edge of txohclk_n. figure 108 below shows the timing diagram of the input and output signals associated with the e1 transmit overhead input interface module in e1 framing format mode. 8.2 e1 receive overhead interface 8.2.1 description of the e1 receive overhead output interface block the e1 receive overhead output interface block will allow an external device to be the consumer of the e1 national bit sequence. this interface provides interface signals and required interface timing to shift out proper data link information at proper time. the receive overhead output interface for a given framer consists of two signals. ? rxohclk_n: the receive overhead output interface clock output signal ? rxoh_n: the receive overhead output interface output signal. the receive overhead output interface clock output pin (rxohclk_n) generates a rising clock edge for each national bit that is configured to carry data link information according to setting of the framer. the data link bits extracted from the incoming e1 frames are outputted from the receive overhead output interface output pin (rxoh_n) before the rising edge of rxohclk_n. the data link equipment should sample and latch the data link bits at the rising edge of rxohclk_n. f igure 108. e1 t ransmit o verhead i nput i nterface t iming 1 2 3 4 5 6 7 8 9 1011121314151617181920 frame # txsync(input) txsync(output) txmsync(input) txmsync(output) txohclk txoh msb sa8 sa7 sa6 sa5 sa4 a si lsb lsb sa4 sa8 sa7 timeslot 0 timeslot 1 1 txserclk txser txsync(out) txsync(in) txohclk txoh
xrt84l38 314 octal t1/e1/j1 framer rev. 1.0.1 the figure below shows block diagram of the receive overhead output interface of xrt84l38. 8.2.2 configure the e1 receive overhead output interface module as source of the national bit sequence in e1 framing format mode the national bit sequence in e1 framing format mode can be extracted and directed to: ? e1 receive overhead output interface block ? e1 receive hdlc controller ? e1 receive serial output interface the purpose of the receive overhead output interface is to permit data link equipment to have direct access to the sa4 through sa8 national bits that are extracted from the incoming e1 frames. independent of the availability of the e1 receive hdlc controller module, the xrt84l38 always output the received national bits through the receive overhead output interface block. the xrt84l38 allows the user to decide on the following: ? how many of the national bits is used to carry the data link information bits ? which of these national bits is used to carry the data link information bits. the receive sa data link select bits of the receive signaling and data link select register (tsdlsr) determine which ones of the national bits are configured as data link bits in e1 framing format mode. depending upon the configuration of the receive signaling and data link select register, either of the following cases may exists: ? none of the received national bits are used to transport the data link information bits (that is, data link channel of xrt84l38 is inactive). ? any combination of between 1 and all 5 of the received national bits are used to transport the data link information bits. the table below shows configuration of the receive sa data link select bits of the receive signaling and data link select register (rsdlsr). f igure 109. b lock d iagram of the e1 r eceive o verhead o utput i nterface of xrt84l38 receive signaling and data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 7 receive sa8 data link select r/w 0 - the received sa8 nation bit is not extracted to the data link interface. 1 - the received sa8 nation bit is extracted to the data link interface. 6 receive sa7 data link select r/w 0 - the received sa7 nation bit is not extracted to the data link interface. 1 - the received sa7 nation bit is extracted to the data link interface. 5 receive sa6 data link select r/w 0 - the received sa6 nation bit is not extracted to the data link interface. 1 - the received sa6 nation bit is extracted to the data link interface. receive overhead output interface rxoh_n rxohclk_n from receive framer block
xrt84l38 315 rev. 1.0.1 octal t1/e1/j1 framer for every received sa bit that is determined to carry data link information, the receive overhead output interface will supply a clock pulse, via the rxohclk_n output pin, such that: ? the receive overhead output interface should update the data on the rxoh_n line before the rising edge of rxohclk_n. ? the external data link equipment interfaced to the receive overhead output interface will sample and latch the data on the rxoh_n line on the rising edge of rxohclk_n. figure 110 below shows the timing diagram of the output signals associated with the e1 receive overhead output interface module in e1 framing format mode. 4 receive sa5 data link select r/w 0 - the received sa5 nation bit is not extracted to the data link interface. 1 - the received sa5 nation bit is extracted to the data link interface. 3 receive sa4 data link select r/w 0 - the received sa4 nation bit is not extracted to the data link interface. 1 - the received sa4 nation bit is extracted to the data link interface. f igure 110. e1 r eceive o verhead o utput i nterface t iming receive signaling and data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 1234567891011121314151617181920 frame # rxsync rxmsync rxohclk rxoh msb sa8 sa7 sa6 sa5 sa4 a si lsb lsb sa4 sa8 sa7 channel 0 channel 1 1 rxserclk rxser rxsync rxohclk rxoh sa5 sa6 if sa4, sa7 and sa8 are selected.
xrt84l38 316 octal t1/e1/j1 framer rev. 1.0.1 9.0 ds1 transmit framer block 9.1 how to configure xrt84l38 to operate in ds1 mode the xrt84l38 octal t1/e1/j1 framer supports ds1, j1 or e1 framing modes. since j1 standard is very similar to ds1 standard with a few minor changes, the j1 framing mode is included as a sub-set of the ds1 framing mode. all eight framers within the xrt84l38 silicon can be individually configured to support ds1, j1 or e1 framing modes. n ote : if transmitting section of one framer is configured to support either one of the framing modes, the receiving section is automatically configured to support the same framing modes. the t1/e1 select bit of the clock select register (csr) controls which framing mode, that is, t1/j1 or e1, supported by the framer. the table below illustrates configurations of the t1/e1 select bit of the clock select register (csr). since j1 and ds1 are two very similar standards, to configure the framer to run in j1 mode, the user has to select ds1 mode by setting the t1/e1 select bit of the clock select register to 1 first. the next step is to set the j1 crc calculation bit of the framing select register (fsr). if this bit is set to 1, the xrt84l38 will do crc-6 calculation in j1 mode. that is, the crc-6 calculation is based on the actual values of all 4,632 bits in ds1 multi-frame including framing bits. if this bit is set to 0, the xrt84l38 will perform crc-6 calculation in ds1 mode. that is, the crc-6 calculation is done based on the actual values of 4,608 payload bits of a ds1 multi-frame and assumes that all the framing bits are one. the table below shows configurations of the j1 crc calculation bit of the framing select register (fsr). the table below provides summary of how to select different operating modes for the xrt84l38 framer. the purpose of the ds1 transmit framer block is to embed and encode user payload data into frames and to route this ds1 frame data to the transmit ds1 liu interface block. please note that the xrt84l38 has eight (8) individual ds1 transmit framer blocks. hence, the following description applies to all eight of these individual transmit ds1 framer blocks. clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 6 t1/e1 select r/w 0 - the xrt84l38 framer is running in e1 mode. 1 - the xrt84l38 framer is running in t1 mode. framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 5 j1 crc calculation r/w in j1 format, crc-6 calculation is done based on the actual values of all payload bits as well as the framing bits. in ds1 format, crc-6 calculation is done based on the payload bits only while assuming all the framing bits are one. 0 - the framer performs crc-6 calculation in ds1 format. 1 - the framer performs crc-6 calculation in j1 format. this feature per - mits the driver to comply with j1 standard. t1/e1 s elect bit of csr j1 crc c alculation bit of fsr t1 set to 1 set to 0 j1 set to 1 set to 1 e1 set to 0 -
xrt84l38 317 rev. 1.0.1 octal t1/e1/j1 framer the purpose of the ds1 transmit framer block is: ? to encode user data, inputted from the terminal equipment into a standard framing format. ? to provide individual data control and signaling conditioning of each ds0 channel. ? to support the transmission of hdlc messages, from the local transmitting terminal, to the remote receiving terminal. ? to transmit indications that the local receive framer has received error frames from the remote terminal. ? to transmit alarm condition indicators to the remote terminal. the following sections discuss functionalities of the ds1 transmit framer block in details. we will also describe how to configure the xrt84l38 to transmit ds1 frames according to system requirement of users. 9.2 how to configure the framer to transmit data in various ds1 framing formats the xrt84l38 octal t1/e1/j1 framer supports the following ds1 framing formats: ? super-frame format (sf), also referred to as d4 framing ? extended super-frame format (esf) ? non-signaling format (n) ? t1dm framing format ? slca96 data link framing format, which use the super-frame (sf) framing structure n ote : if the framer is configured to transmit ds1 frames according to one particular framing format, the receiving side of the framer is also configured to receive ds1 frames according to the same framing format. the user can set the framing format select [2:0] bits of the framing select register (fsr) to determine which ds1 framing format should xrt84l38 be configured to operate. the table below shows configurations of the framing format select [2:0] bits of the framing select register (fsr). 9.2.1 how to configure the framer to input framing alignment bits from different sources framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 2-0 t1 framing select r/w t1 framing select: these read/write bit-fields allow the user to select one of the five t1 framing formats supported by the framer. these framing formats include esf, slca96, sf, n and t1dm mode. n ote : changing of framing format automatically forces the framer to perform re-synchronization. 0 x x bit 2 bit 1 bit 0 1 0 0 1 0 1 1 1 0 1 1 1 framing format esf slc?96 sf n t1dm
xrt84l38 318 octal t1/e1/j1 framer rev. 1.0.1 in ds1 mode, different framing formats are distinguished by different patterns and functions of the framing alignment bit (first bit of a ds1 frame). the xrt84l38 can generate the framing alignment bits internally according to a particular framing format. at the same time, the users can generate the framing alignment bits externally and insert them into the framer through the transmit serial data input interface block via the txser_n pin. it is the user's responsibility to maintain the accuracy and integrity of the framing alignment bits. the user also has to make sure that the framing alignment bits are inserted into the framer at right position and right timing. however, this option is only available when the xrt84l38 is configured to run at a normal back-plane rate of 1.544mbit/s. the framing bit source select bit of the synchronization mux register (smr) controls source of the framing alignment bit. the table below shows configurations of the framing bit source select bit of the synchronization mux register (smr). 9.2.2 how to configure the framer to input crc-6 bits from different sources if the framer is configured to operate in extended super-frame format, the framing bits of frame number 2, 6, 10, 14, 18 and 22 of an esf multi-frame are used as c yclic redundancy check (crc-6) code of the last esf multi-frame. the crc-6 bits are an indicator of the link quality and could be monitored by the user to establish error performance report. the xrt84l38 can generate the crc-6 bits internally by calculating the crc check-sum of all the 4,632 bits in ds1 multi-frame while assuming the framing bits to be one. at the same time, the users can generate the crc-6 bits ex ternally and insert them into the framer through the transmit serial data input interface block via the txser_n pin. it is the user's responsibility to correctly compute the crc-6 bits according to ds1 algorithm. also, the user has to make sure that the crc-6 bits are inserted into the framer at right position and right timing. however, this option is only available when the xrt84l38 is configured to run at a normal back-plane rate of 1.544mbit/s. synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 0 framing bit source r/w framing bit source: this read/write bit-field permits the user to determine where the fram - ing alignment bits should be inserted. 0 - the framing alignment bits are generated and inserted by the framer internally. 1 - if the framer is operating in normal 1.544mbit/s mode, the framing align - ment bits are passed through from the transmit serial data input interface block via the txser_n pin.
xrt84l38 319 rev. 1.0.1 octal t1/e1/j1 framer the crc-6 source select bit of the synchronization mu x register (smr) controls from where to input crc-6 bits into the framer. the table below shows configurations of the crc-6 source select bit of the synchronization mux register (smr). 9.3 how to configure the framer to apply data and signaling conditioning to ds1 payload data on a per-channel basis the xrt84l38 t1/j1/e1 octal framer provides individual control of each of the twenty-four ds0 channels. the user can apply data and signaling conditioning to raw ds1 payload data coming from the terminal equipment on a per-channel basis. the xrt84l38 framer can apply the following changes to raw ds1 pcm data coming from the terminal equipment on a per-channel basis: ? all 8 bits of the input pcm data are inverted ? the even bits of the input pcm data are inverted ? the odd bits of the input pcm data are inverted ? the msb of the input pcm data is inverted ? all input pcm data except the msb are inverted configuration of the xrt84l38 framer to apply the above-mentioned changes to raw ds1 pcm data are controlled by the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each ds0 channel. the xrt84l38 framer can also replace the incoming raw ds1 pcm data from the terminal equipment with pre-defined or user-defined codes. the xrt84l38 supports the following conditioning substitutions: ? busy code - an octet with hexadecimal value of 0x7f ? busy_ts code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number ? vacant code - an octet with hexadecimal value of 0xff ? a-law digital milliwatt code ? u-law digital milliwatt code ? idle code - an octet defined by the value stored in the user idle code register (ucr) ? moof code - mux-out-of-frame code with hexadecimal value of 0x1a ? prbs code - an octet generated by the pseudo-random bit sequence (prbs) generator block of the framer once again, configuration of the xrt84l38 framer to replace raw ds1 pcm data with the above-mentioned coding schemes are controlled by the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each ds0 channel. synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 1 crc-6 source select r/w crc-6 source select: this read/write bit-field permits the user to determine where the crc- 6 bits should be inserted. 0 - the crc-6 bits are g enerated and inserted by the framer internally. 1 - if the framer is operating in normal 1.544mbit/s mode, the crc-6 bits are generated by external equipment and passed through from the trans - mit serial data input interface block via the txser_n pin.
xrt84l38 320 octal t1/e1/j1 framer rev. 1.0.1 finally, the xrt84l38 framer can configure any one or ones of the twenty-four ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each channel determine whether that particular channel is configured as d or e channel. the table below illustrates configurations of the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr). 9.3.1 how to apply user idle code to the ds1 payload data transmit channel control register (tccr) (indirect address = 0xn2h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 3-0 transmit conditioning select r/w 0000 - the input ds1 pcm data of this ds0 channel is unchanged. 0001 - all 8 bits of the input ds1 pcm data of this ds0 channel are inverted. 0010 - the even bits of the input ds1 pcm data of this ds0 channel are inverted. 0011 - the odd bits of the input ds1 pcm data of this ds0 channel are inverted. 0100 - the input ds1 pcm data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). 0101 - the input ds1 pcm data of this ds0 channel are replaced by busy code (0x7f). 0110 - the input ds1 pcm data of this ds0 channel are replaced by vacant code (0xff). 0111 - the input ds1 pcm data of this ds0 channel are replaced by busy_ts code (111xxxxx). 1000 - the input ds1 pcm data of this ds0 channel are replaced by mux- out-of-frame (moof) code with value 0x1a. 1001 - the input ds1 pcm data of this ds0 channel are replaced by the a-law digital milliwatt pattern. 1010 - the input ds1 pcm data of this ds0 channel are replaced by the u- law digital milliwatt pattern. 1011 - the msb bit of the input ds1 pcm data of this ds0 channel is inverted. 1100 - all bits of the input ds1 pcm data of this ds0 channel except msb bit are inverted. 1101 - the input ds1 pcm data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. 1110 - the input ds1 pcm data of this ds0 channel is unchanged. 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 321 rev. 1.0.1 octal t1/e1/j1 framer when the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of a particular ds0 channel are set to 0100, input ds1 pcm data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). the table below shows contents of the user idle code register. let us study the following example of applying the user idle code. in t1dm mode, the time slot 24 of a ds1 frame is used for synchronization and alarm. to generate the t1dm framing mode externally, the user can do the following: ? write the t1dm synchronization word (0xbc) to the user idle code register of the time slot 24. ? set the transmit data conditioning select [3:0] bits of the tccr of channel 24 to "0100". upon doing the above, the payload data of channel 24 will be replaced by the t1dm synchronization code 0xbc. 9.4 how to configure the xrt84l38 framer to apply zero code suppression to ds1 payload data on a per-channel basis in order to guarantee adequate clock recovery from the received pcm data, a minimum "ones density" must be maintained. in the case of an all zero channel, that is, if all the incoming pcm data of a particular ds0 channel from the terminal equipment is zero, the raw pcm data is replaced by a certain pattern that no more than fifteen consecutive zeros will occur. it is known as zero code suppression. the xrt84l38 framer supports three types of zero code suppression schemes: ? at&t bit 7 stuffing - an old coding method that forces bit 7 (the second lsb of a ds0 channel) to a 1 in an all zero channel. ? gte zero code suppression - bit 8 (the lsb of a ds0 channel) is stuffed by 1 in non-signaling frame in an all zero channel. otherwise, bit 7 is stuffed by 1 in signaling frame if the signaling bit is zero. ? dds zero code suppression - an octet with hexadecimal value of 0x98 is used to replace the input data if it is all zero. the transmit zero code suppression select [1:0] bits of the transmit channel control register (tccr) of a particular ds0 channel is used to select which type of zero code suppression scheme is used by the framer. the table below shows configurations of the transmit zero code suppression select [1:0] bits of the transmit channel control register (tccr). 9.5 how to configure the xrt84l38 framer to transmit robbed-bit signaling information user idle code register (ucr) (indirect address = 0xn02h, 0x20h - 0x37h) b it n umber b it n ame b it t ype b it d escription 7-0 user idle code r/w these read/write bit-fields permits the user store any value of idle code into the framer. when the transmit data conditioning select [3:0] bits of tccr register of a particular ds 0 channel are set to 0100, the input ds1 pcm data are replaced by contents of this register and sent to the transmit liu interface. transmit channel control register (tccr) (indirect address = 0xn2h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 5-4 transmit zero code suppression select r/w 00 - the input ds1 pcm data of this ds0 channel is unchanged. no zero code suppression is used. 01 - at&t bit 7 stuffing is used. 10 - gte zero code suppression is used. 11 - dds zero code suppression is used.
xrt84l38 322 octal t1/e1/j1 framer rev. 1.0.1 the xrt84l38 t1/j1/e1 octal framer supports insertion of robbed-bit signaling information into the outgoing ds1 frame. it also supports extraction and substitution of robbed-bit signaling information from the incoming ds1 frame. the following section provides a brief overview of robbed-bit signaling in ds1 mode. 9.5.1 brief discussion of robbed-bit signaling in ds1 framing format signaling is required when dealing with voice and dial-up data services in ds1 applications. traditionally, signaling is provided on a dial-up telephone line, across the talk-path. bit robbing, or stealing the least significant bit (8th bit) in each of the twenty-four voice channels in the signaling frames allows enough bits to signal between the transmitting and receiving end. that is how the name robbed-bit signaling comes from. these ends can be cpe to central office (co) for switched services, or cpe to cpe for pbx-to-pbx connections. signaling is used to tell the receiver where the call or route is destined. the signal is sent through switches along the route to a distant end. common types of signals are: ? on hook ? off hook ? dial tone ? dialed digits ? ringing cycle ? busy tone robbed-bit signaling is supported in three ds1 framing formats: ? super-frame (sf) ? slc?96 ? extended super-frame (esf) in super-frame or slc?96 framing mode, frame number 6 and frame number 12 are signaling frames. in channelized ds1 applications, these frames are used to contain the signaling information. in frame number 6 and 12, the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. the bit in frame 6 is called the a bit and the bit in frame 12 is called the b bit. the combination of a and b defines the state of the call for the particular timeslot that these two bits are located. in extended super-frame framing mode, frame number 6, 12, 18 and 24 are signaling frames. in these frames, the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. the bit in frame 6 is called the a bit, the bit in frame 12 is called the b bit, the bit in frame 18 is called the c bit and the bit in frame 24 is called the d bit. the combination of a, b, c and d defines the state of the call for the particular timeslot that these signaling bits are located. f rame n umber s ignaling b it 6 a 12 b f rame n umber s ignaling b it 6 a 12 b
xrt84l38 323 rev. 1.0.1 octal t1/e1/j1 framer 9.5.2 configure the framer to transmit robbed-bit signaling the xrt84l38 framer supports transmission of robbed-bit signaling in esf, sf and slc?96 framing formats. signaling bits can be inserted into the outgoing ds1 frame through the following: ? signaling data is inserted from transmit signaling control registers (tscr) of each timeslot ? signaling data is inserted from txsig_n pin ? signaling data is embedded into the input pcm data coming from the terminal equipment 9.5.2.1 insert signaling bits from tscr register the four most significant bits of the transmit signaling control register (tscr) of each timeslot can be used to store outgoing signaling data. the user can program these bits through microprocessor access. if the xrt84l38 framer is configure to insert signaling bits from tscr registers, the ds1 transmit framer block will strip off the least significant bits of signaling frames and replace it with the signaling bit stored inside the tscr registers. the insertion of signaling bit into pcm data is done on a per-channel basis. the most significant bit (bit 7) of tscr register is used to store signaling bit a. bit 6 is used to hold signaling bit b. bit 5 is used to hold signaling bit c. bit 4 is used to hold signaling bit d. in sf or slca96 mode, the user can control the xrt84l38 framer to transmit no signaling (transparent), two- code signaling, or four-code signaling. two-code signaling is done by substituting the least significant bit (lsb) of the specific channel in frame 6 and 12 with the content of the signaling bit a of the specific tscr register. n ote : the user should make sure that signaling bit a and signaling bit b of the specific tscr register have the same value. four-code signaling is done by substituting the lsb of channel data in frame 6 with the signaling bit a and the lsb of channel data in frame 12 with the signaling bit b of the specific channel's tscr register. if sixteen-code signaling is selected in sf format, only the signaling bit a and signaling bit b information are used. in esf mode, the user can control the xrt84l38 framer to transmit no signaling (transparent) by disable signaling insertion, two-code signaling, four-code signaling or sixteen code signaling. two-code signaling is done by substituting the least significant bit (lsb) of the specific channel in frame 6, 12, 18 and 24 with the content of the signaling bit a of the specific tscr register. n ote : the user should duplicate the contents of signaling bit a of the specific tscr register to signaling bit b, c and d. four-code signaling is done by substituting the lsb of channel data in frame 6 and frame 18 with the signaling bit a and the lsb of channel data in frame 12 and frame 24 with the signaling bit b of the specific channel's tscr register. n ote : the user should duplicate the contents of signaling bit a of the specific tscr register to signaling bit c and duplicate the contents of signaling bit b of the specific tscr register to signaling bit d. sixteen-code signaling is implemented by substituting the lsb of channel data in frames 6, 12, 18, and 24 with the content of signaling bit a, b, c, and d of tscr register respectively. in n mode, no robbed-bit signaling is allowed and the transmit data stream remains intact. 18 c 24 d f rame n umber s ignaling b it
xrt84l38 324 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the four most significant bits of the transmit signaling control register. 9.5.2.2 insert signaling bits from txsig_n pin the xrt84l38 framer can be configure to insert signaling bits provided by external equipment through the txsig_n pins. this pin is a multiplexed i/o pin with two functions: ? txtsb[0]_n - transmit timeslot number bit [0] output pin ? txsig_n - transmit signaling input pin when the transmit fractional ds1 bit of the transmit interface control register (ticr) is set to 0, this pin is configured as txtsb[0]_n pin, it outputs bit 0 of the timeslot number of the ds1 pcm data that is transmitting. when the transmit fractional ds1 bit of the transmit interface control register (ticr) is set to 1, this pin is configured as txsig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound ds1 frames. figure 111 below is a timing diagram of the txsig_n input pin. please note that the signaling bit a of a certain timeslot coincides with bit 5 of the pcm data; signaling bit b coincides with bit 6 of the pcm data; signaling bit c coincides with bit 7 of the pcm data and signaling bit d coincides with bit 8 (lsb) of the pcm data. transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it n umber b it n ame b it t ype b it d escription 7 signaling bit a r/w this bit is used to store signaling bit a that is sent as the least significant bit of timeslot of frame number 6. 6 signaling bit b r/w this bit is used to store signaling bit b that is sent as the least significant bit of timeslot of frame number 12. 5 signaling bit c r/w this bit is used to store signaling bit c that is sent as the least significant bit of timeslot of frame number 18. 4 signaling bit d r/w this bit is used to store signaling bit d that is sent as the least significant bit of timeslot of frame number 24. f igure 111. t iming d iagram of the t x s ig _ n i nput txserclk txserclk (inv) txser f f input data input data input data input data timeslot 23 timeslot 0 timeslot 5 timeslot 6 c txsig a b d c a b d c a b d c a b d
xrt84l38 325 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the transmit fractional ds1 bit of the transmit interface control register (ticr). 9.5.2.3 insert signaling data from txser_n pin depends on applications, the terminal equipment can embed signaling information into the ds1 pcm data and then send the data to the xrt84l38 framer device. in this case, the user should configure the framer not to insert any signaling data. the input ds1 pcm data will then be directed to the transmit liu interface without any modifications. 9.5.2.4 enable robbed-bit signaling and signaling data source control the transmit signaling control register (tscr) of each channel selects source of signaling data to be inserted into the outgoing ds1 frame and enables robbed-bit signaling. as we mentioned before, the signaling data can be inserted from transmit signaling control registers (tscr) of each timeslot, from the txsig_n input pin or from the txser_n input pin. the transmit signaling data source select [1:0] bits of the transmit signaling control register (tscr) determines from which sources the signaling data is inserted from. the table below shows configurations of the transmit signaling data source select [1:0] bits of the transmit signaling control register (tscr). transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 transmit fractional ds1 r/w this read/write bit-field permits the user to determine which one of the two functions the multiplexed i/o pin of txtsb[0]_n/txsig_n is spotting. 0 - this pin is configured as txtsb[0]_n pin, it outputs bit 0 of the timeslot number of the ds1 pcm data that is transmitting. 1 - this pin is configured as txsig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound ds1 frames transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it n umber b it n ame b it t ype b it d escription 1-0 transmit signaling source select r/w 00 - no signaling data is inserted into the input ds1 pcm data by the framer. however, the user can embed signaling data into ds1 pcm data before routing the pcm data into the framer. 01 - signaling data is inserted into the input ds1 pcm data from tscr register of each timeslot. 10 - signaling data is inserted into the input ds1 pcm data from the txsig_n input pin. 11 - no signaling data is inserted into the input ds1 pcm data by the framer. however, the user can embed signaling data into ds1 pcm data before routing the pcm data into the framer.
xrt84l38 326 octal t1/e1/j1 framer rev. 1.0.1 the robbed-bit signaling enable bit of the transmit signaling control register (tscr) determines whether robbed-bit signaling is available. the table below shows configurations of the robbed-bit signaling enable bit of the transmit signaling control register (tscr). 9.6 how to configure the xrt84l38 framer to generate and transmit alarms and error indications to remote terminal the xrt84l38 t1/j1/e1 octal framer can be configured to monitor quality of received ds1 frames. it can generate error indications if the local receive framer has received error frames from the remote terminal. if corresponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. upon microprocessor interruption, the user can intervene by looking into the error conditions. at the same time, the user can configure the xrt84l38 framer to transmit alarms and error indications to remote terminal. different alarms and error indications will be transmitted depending on the error condition. the section below gives a brief discussion of the error conditions and appropriate alarms that should be generated and transmitted by the xrt84l38 framer. 9.6.1 brief discussion of alarms and error conditions as defined in ansi t1.231 specification, alarm conditions are created from defects. defects are momentary impairments present on the ds1 trunk. if a defect is present for a sufficient amount of time (called the integration time), then the defect becomes an alarm. once an alarm is declared, the alarm is present until after the defect clears for a sufficient period of time. the time it takes to clear an alarm is called the de-integration time. alarms are used to detect and warn maintenance personnel of problems on the ds1 trunk. there are three types of alarms: ? red alarm or service alarm indication (sai) signal ? blue alarm or alarm indication signal (ais) ? yellow alarm or remote alarm indication (rai) signal to explain the error conditions and generation of different alarms, let us create a simple ds1 system model. in this model, a ds1 signal is sourced from the central office (co) through a repeater to the customer premises transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it n umber b it n ame b it t ype b it d escription 1-0 robbed-bit signaling enable r/w 0 - robbed-bit signaling is disabled. no signaling data will be inserted into the input pcm data no matter what the setting of the transmit signaling source select [1:0] bits is. 1 - signaling data is enabled and inserted into the input ds1 pcm data according to setting of the transmit signaling source select [1:0] bits.
xrt84l38 327 rev. 1.0.1 octal t1/e1/j1 framer equipment (cpe). at the same time, a ds1 signal is routed from the cpe to the repeater and back to the central office. figure 112 below shows the simple ds1 system model. when the e1 system runs normally, that is, when there is no loss of signal (los) or loss of frame (lof) detected in the line, no alarm will be generated. sometimes, intermittent outburst of electrical noises on the line might result in bipolar violation or bit errors in the incoming signals, but these errors in general will not trigger the equipment to generate alarms. they will at most trigger the framer to generate interrupts which would cause the local microprocessor to create performance reports of the line. now, consider a case in which the e1 line from the repeater to cpe is broken or interrupted, resulting in completely loss of incoming data or severely impaired signal quality. upon detection of loss of signal (los) or loss of frame (lof) condition, the cpe will generate an internal red alarm, also known as the service alarm indication. this alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. when the cpe is in the red alarm state, it will transmit the yellow alarm to the repeater indicating the loss of an incoming signal or loss of frame synchronization. this yellow alarm informs the repeater that there is a f igure 112. s imple d iagram of ds1 s ystem m odel ds1 receive framer block ds1 transmit framer block ds1 receive framer block ds1 transmit framer block ds1 transmit section ds1 transmit section ds1 receive section ds1 receive section co repeater cpe simple ds1 system model
xrt84l38 328 octal t1/e1/j1 framer rev. 1.0.1 problem further down the line and its transmission is not being received at the cpe. figure ? below illustrates the scenario in which the e1 connection from the repeater to cpe is broken. the repeater, upon detection of yellow alarm originated from the cpe, will transmit a blue alarm, also known as alarm indication signal (ais) to the co. blue alarm is an all ones pattern indicating that the equipment is functioning but unable to offer service due to failures originated from remote side. it is sent such that the equipment downstream will not lose clock synchronization even though no meaningful data is received. figure f igure 113. g eneration of y ellow a larm by the cpe upon detection of line failure ds1 receive framer block ds1 transmit framer block ds1 receive framer block ds1 transmit framer block ds1 transmit section ds1 transmit section ds1 receive section ds1 receive section co repeater cpe the ds1 line is broken cpe declares red alarm internally yellow alarm
xrt84l38 329 rev. 1.0.1 octal t1/e1/j1 framer ? below illustrates this scenario in which the repeater is sending an ais to co upon detection of yellow alarm originated from the cpe. now let us consider another scenario in which the ds1 line between co and the repeater is broken. again, upon detection of loss of signal (los) or loss of frame (lof) condition, the repeater will generate an internal red alarm. this alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. the repeater will also send an all ones ais pattern downstream to the cpe. the cpe uses the ais signal to recover received clock and remain in synchronization with the system. upon detecting the incoming ais signal, the cpe will generate a yellow alarm to the repeater to indicate the loss of incoming signal. figure ? below f igure 114. g eneration of ais by the r epeater upon detection of y ellow a larm originated by the cpe ds1 receive framer block ds1 transmit framer block ds1 receive framer block ds1 transmit framer block ds1 transmit section ds1 transmit section ds1 receive section ds1 receive section co repeater cpe the ds1 line is broken cpe declares red alarm internally yellow alarm repeater detects yellow alarm and generate ais to co ais
xrt84l38 330 octal t1/e1/j1 framer rev. 1.0.1 illustrates this scenario in which the repeater is sending an ais to the cpe and the cpe is sending a yellow alarm back to the repeater. 9.6.2 how to configure the framer to transmit ais as we discussed in the previous section, alarm indication signal (ais) or blue alarm is transmitted by the intermediate node to indicate that the equipment is still functioning but unable to offer services. it is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. the xrt84l38 framer can generate two types of ais: ? framed ais ? unframed ais unframed ais is an all ones pattern. if unframed ais is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received ais signal. however, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare loss of frame (lof). on the other hand, the payload portion of a framed ais pattern is all ones. however, a framed ais pattern still has correct framing bits. therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. in this case, no lof or red alarm will be declared. f igure 115. g eneration of y ellow a larm by the cpe upon detection of ais originated by the r epeater ds1 receive framer block ds1 transmit framer block ds1 receive framer block ds1 transmit framer block ds1 transmit section ds1 transmit section ds1 receive section ds1 receive section co repeater cpe the ds1 line is broken repeater declares red alarm internally yellow alarm repeater detects yellow alarm and generate ais to co ais
xrt84l38 331 rev. 1.0.1 octal t1/e1/j1 framer the transmit alarm indication signal select [1:0] bits of the alarm generation register (agr) enable the two types of ais transmission that are supported by the xrt84l38 framer. the table below shows configurations of the transmit alarm indication signal select [1:0] bits of the alarm generation register (agr). 9.6.3 how to configure the framer to generate red alarm upon detection of loss of signal (los) or loss of frame (lof) condition, the repeater will generate an internal red alarm when enabled. this alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. the loss of frame declaration enable bit of the alarm generation register (agr) enable the generation of red alarm. the table below shows configurations of the of frame declaration enable bit of the alarm generation register (agr). 9.6.4 how to configure the framer to transmit yellow alarm upon detection of loss of signal (los) or loss of frame (lof) condition, the receiver will transmit the yellow alarm back to the source indicating the loss of an incoming signal. this yellow alarm informs the source that there is a problem further down the line and its transmission is not being received at the destination. the xrt84l38 framer supports transmission of yellow alarm when running at the following framing formats: ? sf mode ? esf mode ? n mode ? t1dm mode yellow alarm is transmitted in different forms for various framing formats. the yellow alarm generation select [1:0] bits of the alarm generation register (agr) enable transmission of different types of yellow alarm that are supported by the xrt84l38 framer. 9.6.4.1 transmit yellow alarm in sf mode alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 3-2 transmit ais select r/w these read/write bit-fields allows the user to choose which one of the two ais pattern supported by the xrt84l38 framer will be transmitted. 00 - no ais alarm is generated. 01 - enable unframed ais alarm of all ones pattern. 10 - enable framed ais alarm of all ones pattern except for framing bits. 11 - no ais alarm is generated. alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 6 loss of frame declaration enable r/w this read/write bit-field permits the framer to declare red alarm in case of loss of frame alignment (lof). when receiver module of the framer detects loss of frame alignment in the incoming data stream, it will generate a red alarm. the framer will also generate an rxlofs interrupt to notify the microprocessor that an lof condition is occurred. a yellow alarm is then returned to the remote transmitter to report that the local receiver detects lof. 0 - red alarm declaration is disabled. 1 - red alarm declaration is enabled.
xrt84l38 332 octal t1/e1/j1 framer rev. 1.0.1 in sf mode, the xrt84l38 supports transmission of yellow alarm in two ways. when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 01 or 11, the second msb of all ds0 channels is transmitted as zero. this is yellow alarm for ds1 standard. when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 10, the framing bit of frame 12 is transmitted as one. this is yellow alarm for j1 standard. 9.6.4.2 transmit yellow alarm in esf mode in esf mode, the xrt84l38 transmits yellow alarm on the 4kbit/s data link channel. the facility data link bits are sent in the pattern of eight ones followed by eight zeros. the number of repetitions of this pattern depends on the duration of yellow alarm generation select [1:0] bits of the alarm generation register. when these select bits are set to 01 or 11, the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to trans - mit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. when these select bits are set to 10, bit 1 of the yellow alarm generation select forms a pulse that controls the duration of yellow alarm transmission. the alarm continues until bit 1 goes low. when these select bits are set to 01, the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to trans - mit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. 9.6.4.3 transmit yellow alarm in n mode in n mode, when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 01, 10 or 11, the second msb of all ds0 channels is transmitted as zero. 9.6.4.4 transmit yellow alarm in t1dm mode in t1dm mode, when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 01, 10 or 11, the yellow alarm bit (the third lsb of timeslot 23) is set to zero.the table below shows configurations of the yellow alarm generation select [1:0] bits of the alarm generation register (agr).
xrt84l38 333 rev. 1.0.1 octal t1/e1/j1 framer ) alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 5-4 yellow alarm generation select r/w 00 - transmission of yellow alarm is disabled. 01 - the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero. 10 - the framer transmits yellow alarm by sending the super-frame align - ment bit (fs) of frame 12 as one. 11 - the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero. n mode: 00 - transmission of yellow alarm is disabled. 01, 10 or 11 - the framer transmits yellow alarm by converting the second msb of all outgoing twenty-four ds0 channel into zero. esf mode: when the framer is in esf mode, it transmits yellow alarm pattern of eight ones followed by eight zeros (1111_ 1111_0000_0000) through the 4kbit/s data link bits. 00 - transmission of yellow alarm is disabled. 01 - the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. 10 - bit 1 of the yellow alarm generation select forms a pulse that controls the duration of yellow alarm transmission. the alarm continues until bit 1 goes low. 11 - the following scenario will happen: 1. if bit 0 of yellow alarm generation select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4kbit/s data link, the alarm is transmitted for 255 patterns. 2. if bit 0 of yellow alarm generation select forms a pulse width longer than the time required to transmit 255 patterns on the 4kbit/s data link, the alarm continues until bit 0 goes low. 3. a second pulse on bit 0 of yellow alarm generation select during an alarm transmission resets the pattern counter. the framer will send another 255 patterns of the yellow alarm. t1dm mode: 00 - transmission of yellow alarm is disabled. 01, 10 or 11 - the framer transmits yellow alarm by setting the yellow alarm bit (y-bit) to zero.
xrt84l38 334 octal t1/e1/j1 framer rev. 1.0.1 10.0 ds1 receive framer block 10.1 how to configure xrt84l38 to operate in ds1 mode the xrt84l38 octal t1/e1/j1 framer supports ds1, j1 or e1 framing modes. since j1 standard is very similar to ds1 standard with a few minor changes, the j1 framing mode is included as a sub-set of the ds1 framing mode. all eight framers within the xrt84l38 silicon can be individually configured to support ds1, j1 or e1 framing modes. n ote : if transmitting section of one framer is configured to support either one of the framing modes, the receiving section is automatically configured to support the same framing modes. the t1/e1 select bit of the clock select register (csr) controls which framing mode supported by the framer. the table below illustrates configurations of the t1/e1 select bit of the clock select register (csr). since j1 and ds1 are two very similar standards, to configure the framer to run in j1 mode, the user has to select ds1 mode by setting the t1/e1 select bit of the clock select register to 1 first. the next step is to set the j1 crc calculation bit of the framing select register (fsr). if this bit is set to 1, the xrt84l38 will do crc-6 calculation in j1 mode. that is, the crc-6 calculation is based on the actual values of all 4,632 bits in ds1 multi-frame including framing bits. if this bit is set to 0, the xrt84l38 will perform crc-6 calculation in ds1 mode. that is, the crc-6 calculation is done based on the actual values of 4,608 payload bits of a ds1 multi-frame and assumes that all the framing bits are one. the table below shows configurations of the j1 crc calculation bit of the framing select register (fsr). the table below provides summary of how to select different operating modes for the xrt84l38 framer. the purpose of the ds1 receive framer block is to accept framed ds1 data from the receive ds1 liu interface block. the receive framer block will identify frame boundary and establish framing alignment synchronization of the incoming ds1 frame. the receive framer block will then decode and extract user payload data from received frames please note that the xrt84l38 has eight (8) individual ds1 transmit clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 6 t1/e1 select r/w 0 - the xrt84l38 framer is running in e1 mode. 1 - the xrt84l38 framer is running in t1 mode. framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 5 j1 crc calculation r/w in j1 format, crc-6 calculation is done based on the actual values of all payload bits as well as the framing bits. in ds1 format, crc-6 calculation is done based on the payload bits only while assuming all the framing bits are one. 0 - the framer will perform crc-6 calculation in ds1 format. 1 - the framer will perform crc-6 calculation in j1 format. this feature permits the driver to comply with j1 standard. t1/e1 s elect bit of csr j1 crc c alculation bit of fsr t1 set to 1 set to 0 j1 set to 1 set to 1 e1 set to 0 -
xrt84l38 335 rev. 1.0.1 octal t1/e1/j1 framer framer blocks. hence, the following description applies to all eight of these individual transmit ds1 framer blocks. the purpose of the ds1 receive framer block is: ? to identify frame boundary and establish framing alignment synchronization. ? to decode user data, inputted from the receive ds1 liu interface block to the terminal equipment. ? to provide individual data control and signaling conditioning of each ds0 channel. ? to support the receiving and extraction of hdlc messages, from the remote receiving terminal. ? to detect error conditions and generate indications and interrupts to notify the user that the local receive framer has received error frames from the remote terminal. ? to receive and decode alarm condition indicators from the remote terminal. the following sections discuss functionalities of the ds1 receive framer block in details. 10.2 how to configure the framer to receive data in various ds1 framing formats the xrt84l38 octal t1/e1/j1 framer supports the following ds1 framing formats: ? super-frame format (sf), also referred to as d4 framing ? extended super-frame format (esf) ? non-signaling format (n) ? t1dm framing format ? slc?96 data link framing format, which use the super-frame (sf) framing structure n ote : if the framer is configured to receive ds1 frames according to one particular framing format, the transmitting side of the framer is also configured to transmit ds1 frames according to the same framing format. the user can set the framing format select [2:0] bits of the framing select register (fsr) to determine which ds1 framing format should xrt84l38 be configured to operate. the table below shows configurations of the framing format select [2:0] bits of the framing select register (fsr). framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 2-0 t1 framing select r/w these read/write bit-fields allow the user to select one of the five t1 framing formats supported by the framer. these framing formats include esf, slc ? 96, sf, n and t1dm mode. n ote : changing of framing format will automatically force the framer to perform re-synchronization. 0 x x bit 2 bit 1 bit 0 1 0 0 1 0 1 1 1 0 1 1 1 framing format esf slc?96 sf n t1dm
xrt84l38 336 octal t1/e1/j1 framer rev. 1.0.1 10.3 how to configure the framer to apply data and signaling conditioning to received ds1 payload data on a per-channel basis the xrt84l38 t1/j1/e1 octal framer provides individual control of each of the twenty-four ds0 channels. the user can apply data and signaling conditioning to the received ds1 payload data coming from the ds1 liu receive block on a per-channel basis. the xrt84l38 framer can apply the following changes to the received ds1 payload data coming from the terminal equipment on a per-channel basis: ? all 8 bits of the received payload data are inverted ? the even bits of the received payload data are inverted ? the odd bits of the received payload data are inverted ? the msb of the received payload data is inverted ? all received payload data except the msb are inverted configurations of the xrt84l38 framer to apply the above-mentioned changes to the received ds1 payload data are controlled by the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each ds0 channel. the xrt84l38 framer can also replace the incoming ds1 payload data from the ds1 liu receive block with pre-defined or user-defined codes. the xrt84l38 supports the following conditioning substitutions: ? busy code - an octet with hexadecimal value of 0x7f ? busy_ts code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number ? vacant code - an octet with hexadecimal value of 0xff ? a-law digital milliwatt code ? u-law digital milliwatt code ? idle code - an octet defined by the value stored in the user idle code register (ucr) ? moof code - mux-out-of-frame code with hexadecimal value of 0x1a ? prbs code - an octet generated by the pseudo-random bit sequence (prbs) generator block of the framer once again, configuration of the xrt84l38 framer to replace the received ds1 payload data with the above- mentioned coding schemes are controlled by the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each ds0 channel. finally, the xrt84l38 framer can configure any one or ones of the twenty-four ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each channel determine whether that particular channel is configured as d or e channel.
xrt84l38 337 rev. 1.0.1 octal t1/e1/j1 framer the table below illustrates configurations of the receive data conditioning select [3:0] bits of the receive channel control register (rccr). when the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of a particular ds0 channel are set to 0100, the received ds1 payload data of this ds0 channel are replaced by the octet stored in the receive user idle code register (rucr). the table below shows contents of the receive user idle code register. 10.4 how to configure the xrt84l38 framer to apply zero code suppression to received ds1 payload data on a per-channel basis receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it n umber b it n ame b it t ype b it d escription 3-0 receive conditioning select r/w 0000 - the received ds1 payload data of this ds0 channel is unchanged. 0001 - all 8 bits of the input ds1 payload data of this ds0 channel are inverted. 0010 - the even bits of the input ds1 payload data of this ds0 channel are inverted. 0011 - the odd bits of the input ds1 payload data of this ds0 channel are inverted. 0100 - the input ds1 payload data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). 0101 - the input ds1 payload data of this ds0 channel are replaced by busy code (0x7f). 0110 - the input ds1 payload data of this ds0 channel are replaced by vacant code (0xff). 0111 - the input ds1 payload data of this ds0 channel are replaced by busy_ts code (111xxxxx). 1000 - the input ds1 payload data of this ds0 channel are replaced by mux-out-of-frame (moof) code with value 0x1a. 1001 - the input ds1 payload data of this ds0 channel are replaced by the a-law digital milliwatt pattern. 1010 - the input ds1 payload data of this ds0 channel are replaced by the u-law digital milliwatt pattern. 1011 - the msb bit of the input ds1 payload data of this ds0 channel is inverted. 1100 - all bits of the input ds1 payload data of this ds0 channel except msb bit are inverted. 1101 - the input ds1 payload data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. 1110 - the input ds1 payload data of this ds0 channel is unchanged. 1111 - this c hannel is configured as d or e timeslot. receive user idle code register (ucr) (indirect address = 0xn02h, 0x80h - 0x97h) b it n umber b it n ame b it t ype b it d escription 7-0 user idle code r/w these read/write bit-fields permits the user store any value of idle code into the framer. when the receive data conditioning select [3:0] bits of rccr register of a particular ds0 channel are set to 0100, the received ds1 payload data are replaced by contents of this register and sent to the terminal equipment.
xrt84l38 338 octal t1/e1/j1 framer rev. 1.0.1 in order to guarantee adequate clock recovery from the received pcm data, a minimum "ones density" must be maintained. in the case of an all zero channel, that is, if all the incoming pcm data of a particular ds0 channel from the terminal equipment is zero, the raw pcm data is replaced by a certain pattern that no more than fifteen consecutive zeros will occur. it is known as zero code suppression. in the receive end, the user needs to know what type of zero code suppression scheme is applied on the receiving data. in this way, a correct decoding method or the reverse of zero code suppression can be done to extract the payload data from the ds1 liu receive block. the xrt84l38 framer supports three types of zero code suppression schemes: ? at&t bit 7 stuffing - an old coding method that forces bit 7 (the second lsb of a ds0 channel) to a 1 in an all zero channel. ? gte zero code suppression - bit 8 (the lsb of a ds0 channel) is stuffed by 1 in non-signaling frame in an all zero channel. otherwise, bit 7 is stuffed by 1 in signaling frame if the signaling bit is zero. ? dds zero code suppression - an octet with hexadecimal value of 0x98 is used to replace the input data if it is all zero. the receive zero code suppression select [1:0] bits of the receive channel control register (rccr) of a particular ds0 channel is used to select which type of zero code suppression scheme is applied to the received ds1 payload data. the table below shows configurations of the receive zero code suppression select [1:0] bits of the receive channel control register (rccr). 10.5 how to configure the xrt84l38 framer to extract robbed-bit signaling information the xrt84l38 t1/j1/e1 octal framer supports insertion of robbed-bit signaling information into the outgoing ds1 frame. it also supports extraction and substitution of robbed-bit signaling information from the incoming ds1 frame. the following section describes how does the xrt84l38 framer extract and substitute robbed-bit signaling in ds1 mode. 10.5.1 configure the framer to receive and extract robbed-bit signaling the xrt84l38 framer supports receiving and extraction of robbed-bit signaling in esf, sf and slc?96 framing formats. the receive signaling extraction control [1:0] bits of the receive signaling control register (rscr) of each channel select either: ? no signaling extraction ? two-code signaling ? four-code signaling or ? sixteen-code signaling in sf or slca96 mode, the receive signaling extraction control [1:0] bits can select no signaling (transparent), two-code signaling, or four-code signaling. two-code signaling decoding is done by stripping the least significant bit (lsb) of the specific channel in frame 6 and 12 and stores it into the signaling bit a position of rsra register array. four-code signaling is done by stripping the lsb of channel data in frame 6 and the lsb of channel data in frame 12, and store them into signaling bit a and signaling bit b position of rsra receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it n umber b it n ame b it t ype b it d escription 5-4 receive zero code suppression select r/w 00 - the received ds1 payload data of this ds0 channel is unchanged. no zero code suppression is used. 01 - at&t bit 7 stuffing is used. 10 - gte zero code suppression is used. 11 - dds zero code suppression is used.
xrt84l38 339 rev. 1.0.1 octal t1/e1/j1 framer register array respectively. if 16-code signaling is selected in sf format, only the signaling bit a and signaling bit b positions are filled. in esf mode, the receive signaling extraction control [1:0] bits can select no signaling (transparent), two- code signaling, four-code, or sixteen-code signaling. two-code signaling decoding is done by stripping the least significant bit (lsb) of the specific channel in frame 6, 12, 18 and 24 and stores it into the signaling bit a position of rsra register array. four-code signaling is done by stripping the lsb of channel data in frame 6 and frame 18 and the lsb of channel data in frame 12 and 24, and store them into signaling bit a and signaling bit b position of rsra register array respectively. sixteen-code signaling is implemented by stripping the lsb of channel data in frames 6, 12, 18, and 24 and stores them into the signaling bit a, signaling bit b, signaling bit c and signaling bit d position of rsra register array respectively. the table below shows configurations of the receive signaling extraction control [1:0] bits of the receive signaling control register. upon receiving and extraction of signaling bits from the incoming ds1 frames, the xrt84l38 framer compares the signaling bits with the previously received ones. if there is a change of signaling data, a signaling update (sig) interrupt request may be generated at the end of a ds1 multi-frame. the user can thus be notified of a change of signaling data event. to enable the signaling update interrupt, the signaling change interrupt enable bit of the framer interrupt enable register (fier) has to be set. in addition, the t1/e1 framer interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the signaling change interrupt enable bit of the framer interrupt enable register. the table below shows configurations of the t1/e1 framer interrupt enable bit of the block interrupt enable register. receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xb7h) b it n umber b it n ame b it t ype b it d escription 1-0 signaling extraction control r/w 00 - the xrt84l38 framer does not extract signaling information from incoming ds1 payload data. 01 - the xrt84l38 framer extracts sixteen-code signaling information from incoming ds1 payload data. 10 - the xrt84l38 framer extracts four-code signaling information from incoming ds1 payload data. 11 - the xrt84l38 framer extracts two-code signaling information from incoming ds1 payload data. framer interrupt enable register (fier) (indirect address = 0xnah, 0x05h) b it n umber b it n ame b it t ype b it d escription 5 signaling change interrupt enable r/w 0 - the signaling update interrupt is disabled. 1 - the signaling update interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 1 t1/e1 framer interrupt enable r/w 0 - every interrupt generated by the framer interrupt status register (fisr) is disabled. 1 - every interrupt generated by the framer interrupt status register (fisr) is enabled.
xrt84l38 340 octal t1/e1/j1 framer rev. 1.0.1 when these interrupt enable bits are set and the signaling information received is changed, the ds1 receive framer block will set the signaling updated status bit of the framer interrupt status register (fisr) to one. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to- clear operation by the microprocessor is required to reset these status indicators. the table below shows the signaling update status bits of the framer interrupt status register. now, there is only one problem remains. since there are twenty-four ds0 channels in ds1, how do we know signaling information of which channel is changed? to solve this problem, the xrt84l38 provides three 8-bit signaling change registers to indicate the channel(s) which signaling data change had occurred over the last ds1 multi-frame period. each bit of the signaling change registers represents one timeslot of the ds1 frame. if any particular bit is zero, it means there is no change of signaling data occurred in that particular timeslot over the last ds1 multi-frame period. if any particular bit is one, it means there is change of signaling data occurred over the last ds1 multi-frame period. the table below shows configurations of the signaling change registers. by reading contents of the signaling update status bits of the framer interrupt status register and the signaling change registers, the user can clearly identify which one(s) of the twenty-four ds0 channels has changed signaling information over the last multi-frame period. depending on configurations of the xrt84l38 framer, the signaling bits can be extracted from the incoming ds1 frame and direct to all or any one of the following destinations: ? signaling data is stored to receive signaling register array (rsra) of each channel ? signaling data is sent to the terminal equipment through the receive signaling output pin (rxsig_n) ? signaling data is embedded into the output pcm data sending towards the terminal equipment through the receive serial output pin (rxser_n) the follow sections discuss how to configure the xrt84l38 framer to extract signaling information bits and send them to different destinations. 10.5.1.1 store signaling bits into rsra register array the four least significant bits of the receive signaling register array (rsra) of each timeslot can be used to store received signaling data. the user can read these bits through microprocessor access. if the xrt84l38 framer is configure to extract signaling bits from incoming ds1 payload data, the ds1 receive framer block will strip off the least significant bits of signaling frames and store them into appropriate locations of the rsra. framer interrupt status register (fisr) (indirect address = 0xnah, 0x04h) b it n umber b it n ame b it t ype b it d escription 5 signaling updated rur / wc 0 - there is no change of signaling information in the incoming ds1 pay - load data. 1 - there is change of signaling information in the incoming ds1 payload data. signaling change registers (scr) (indirect address = 0xn0h, 0x0dh - 0x0fh) l ocation \ b it b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 0 xn 0h - 0 x 0dh c h 0 c h 1 c h 2 c h 3 c h 4 c h 5 c h 6 c h 7 0xn0h - 0x0eh ch 8 ch 9 ch 10 ch 11 ch 12 ch 13 ch 14 ch 15 0xn0h - 0x0fh ch 16 ch 17 ch 18 ch 19 ch 20 ch 21 ch 22 ch 23
xrt84l38 341 rev. 1.0.1 octal t1/e1/j1 framer the extraction of signaling bit from ds1 pcm data is done on a per-channel basis. the bit 3 of rsra register is used to hole signaling bit a. bit 2 is used to hold signaling bit b. bit 1 is used to hold signaling bit c. bit 0 is used to hold signaling bit d. the table below shows the four least significant bits of the receive signaling register array. 10.5.1.2 outputting signaling bits through rxsig_n pin the xrt84l38 framer can be configure to output extracted signaling bits to external equipment through the rxsig_n pins. this pin is a multiplexed i/o pin with two functions: ? rxtsb[0]_n - receive timeslot number bit [0] output pin ? rxsig_n - receive signaling output pin when the receive fractional ds1 bit of the receive interface control register (ticr) is set to 0, this pin is configured as rxtsb[0]_n pin, it outputs bit 0 of the timeslot number of the ds1 pcm data that is receiving. when the receive fractional ds1 bit of the receive interface control register (ticr) is set to 1, this pin is configured as rxsig_n pin, it acts as an output source for the signaling bits to be received in the inbound ds1 frames. the table below shows configurations of the receive fractional ds1 bit of the receive interface control register (ticr). figure 116 below is a timing diagram of the rxsig_n output pin. please note that the signaling bit a of a certain timeslot coincides with bit 3 of the received serial output data; signaling bit b coincides with bit 2 of receive signaling register array (rsra) (indirect address = 0xn4h, 0x00h - 0x17h) b it n umber b it n ame b it t ype b it d escription 3 signaling bit a r/w this bit is used to store signaling bit a that is received and extracted as the least significant bit of timeslot of frame number 6. 2 signaling bit b r/w this bit is used to store signaling bit b that is received and extracted as the least significant bit of timeslot of frame number 12. 1 signaling bit c r/w this bit is used to store signaling bit c that is received and extracted as the least significant bit of timeslot of frame number 18. 0 signaling bit d r/w this bit is used to store signaling bit d that is received and extracted as the least significant bit of timeslot of frame number 24. receive interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 receive fractional ds1 r/w this read/write bit-field permits the user to determine which one of the two functions the multiplexed i/o pin of rxtsb[0]_n/rxsig_n is spotting. 0 - this pin is configured as rxtsb[0]_n pin, it outputs bit 0 of the timeslot number of the ds1 pcm data that is receiving. 1 - this pin is configured as rxsig_n pin, it acts as an output source for the signaling bits to be received in the inbound ds1 frames
xrt84l38 342 octal t1/e1/j1 framer rev. 1.0.1 the received serial output data; signaling bit c coincides with bit 1 of the received serial output data and signaling bit d coincides with bit 0 of the received serial output data. the receive signaling output enable bit of the receive signaling control register (rscr) determines whether the extracted signaling bits will be sent through the receive signaling output pin (rxsig_n) to external equipments. the table below shows configurations of the receive signaling output enable bit of the receive signaling control register. 10.5.1.3 send signaling data through rxser_n pin as mentioned in the above sections, signaling information embedded in the incoming ds1 pcm data can be sent to either the rsra register array and/or sent through the receive signaling output pin, at the same time, the signaling data will be directed to the receive serial data output pin together with other incoming ds1 payload data. the external equipment can thus still extract signaling data from the received ds1 payload data separately. 10.5.1.4 signaling data substitution after channel conditioning, the signaling conditioning can be optionally enabled by the rscr registers. the actual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the receive substitution signaling register (rssr). to enable signaling substitution, the receive signaling substitution enable bit of the receive signaling control register (rscr) has to be set to one. the table below shows configuration of the receive signaling substitution enable bit of the receive signaling control register. f igure 116. t iming d iagram of the r x s ig _ n o utput pin receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xb7h) b it n umber b it n ame b it t ype b it d escription 5 receive signaling output enable r/w 0 - the xrt84l38 framer w ill not s end extracted signaling bits from the incoming ds1 payload data to external equipment through the receive signaling output pin (rxsig_n). 1 - the xrt84l38 framer will send extracted signaling bits from the incom - ing ds1 payload data to external equipment through the receive signaling output pin (rxsig_n). receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xb7h) b it n umber b it n ame b it t ype b it d escription 6 receive signaling substitution enable r/w 0 - signaling substitution is disabled. the xrt84l38 framer will not replace extracted signaling bits from the incoming ds1 payload data with all ones or with signaling bits stored in rssr registers. 1 - signaling substitution is enabled. the xrt84l38 framer will replace extracted signaling bits from the incoming ds1 payload data with all ones or with signaling bits stored in rssr registers. rxserclk rxser rxsig input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 c a b d c a b d c a b d c a b d
xrt84l38 343 rev. 1.0.1 octal t1/e1/j1 framer as mentioned before, the actual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the receive substitution signaling register (rssr). the table below shows configurations of the receive substitution signaling register. in sf or slc?96 mode, the receive signaling substitution control [1:0] bits can select all ones substitution, two-code signaling substitution, or four-code signaling substitution. the xrt84l38 framer can substitute received signaling bits with all ones. two-code signaling substitution is done by substituting the least significant bit (lsb) of the specific channel in frame 6 and 12 with the content of the sig2-a bit of the receive substitution signaling register (rssr). four-code signaling substitution is done by substituting the lsb of channel data in frame 6 with the sig4-a bit and the lsb of channel data in frame 12 with the sig4-b bit of the rssr register. if 16-code signaling substitution is selected in sf format, only the sig16-a bit and sig16-b bit are used. in esf mode, the receive signaling substitution control [1:0] bits can select all ones substitution, two-code signaling substitution, four-code signaling substitution, or sixteen-code signaling. the xrt84l38 framer can substitute received signaling bits with all ones. two-code signaling substitution is done by substituting the lsb of the specific channel in frame 6, 12, 18, and 24 with the content of the sig2-a bit of the register. four-code signaling substitution is done by substituting the lsb of channel data in frames 6 and 18 with the sig4-a bit and the lsb of channel data in frames 12 and 24 with the sig4-b bit of the rssr register. sixteen-code signaling substitution is implemented by substituting the lsb of channel data in frames 6, 12, 18, and 24 with the content of sig16-a, sig16-b, sig16-c, and sig16-d bits of rssr register respectively. receive substitution signaling register (rssr) (indirect address = 0xn02h, 0x80h - 0x97h) b it n umber b it n ame b it t ype b it d escription 7-4 reserved r/w 3 sig16-a sig4-a sig2-a sixteen-code signaling bit a four-code signaling bit a two-code signaling bit a 2 sig16-b sig4-b sig2-a sixteen-code signaling bit b four-code signaling bit b two-code signaling bit a 1 sig16-c sig4-a sig2-a sixteen-code signaling bit c four-code signaling bit a two-code signaling bit a 0 sig16-d sig4-b sig2-a sixteen-code signaling bit d four-code signaling bit b two-code signaling bit a
xrt84l38 344 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the receive signaling substitution control [1:0] bits of the receive signaling control register. 10.6 how to configure the framer to detect alarms and error conditions the xrt84l38 t1/j1/e1 octal framer can be configured to monitor quality of received ds1 frames. it can generate error indicators if the local receive framer has received error frames from the remote terminal. if corresponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. upon microprocessor interruption, the user can intervene by looking into the error conditions. at the same time, the user can configure the xrt84l38 framer to transmit alarms and error indications to remote terminal. different alarms and error indications will be transmitted depending on the error condition. the section below gives a brief discussion of the error conditions that can be detected by the xrt84l38 framer and error indications that will be generated. 10.6.1 how to configure the framer to detect ais alarm as we discussed before, transmission of alarm indication signal (ais) or blue alarm by the intermediate node indicates that the equipment is still functioning but unable to offer services. it is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. the xrt84l38 framer can detect two types of ais in ds1 mode: ? framed ais ? unframed ais unframed ais is an all ones pattern. if unframed ais is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received ais signal. however, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare loss of frame (lof). on the other hand, the payload portion of a framed ais pattern is all ones. however, a framed ais pattern still has correct framing bits. therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. in this case, no lof or red alarm will be declared. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming ds1 frames for ais. ais alarm condition are detected and declared according to the following procedure: 1. the incoming ds1 frames are monitored for ais detection. ais detection is defined as an unframed or framed pattern with less than three zeros in two consecutive frames. 2. an ais detection counter within the receive framer block of the xrt84l38 counts the occurrences of ais detection over a 6 ms interval. it will indicate a valid ais flag when twenty-two or more of a possible twenty- four ais are detected. receive signaling control register (rscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it n umber b it n ame b it t ype b it d escription 3-2 receive signaling substitution control r/w 00 - the received signaling bits are replaced by all ones and send to the external equipment. 01 - two-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. 10 - four-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. 11 - sixteen-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. n ote : in sf mode, this option is disabled.
xrt84l38 345 rev. 1.0.1 octal t1/e1/j1 framer 3. each 6 ms interval with a valid ais flag increments a flag counter which declares ais alarm when 255 valid flags have been collected. therefore, ais condition has to be persisted for 1.53 seconds before ais alarm condition is declared by the xrt84l38 framer. if there is no valid ais flag over a 6ms interval, the alarm indication logic will decrement the flag counter. the ais alarm is removed when the counter reaches 0. that is, ais alarm will be removed if over 1.53 seconds, there is no valid ais flag. the alarm indication signal detection select [1:0] bits of the alarm generation register (agr) enable the two types of ais detection that are supported by the xrt84l38 framer. the table below shows configurations of the alarm indication signal detection select [1:0] bits of the alarm generation register (agr). if detection of unframed or framed ais alarm is enabled by the user and if ais is present in the incoming ds1 frame, the xrt84l38 framer can generate a receive ais state change interrupt associated with the setting of receive ais state change bit of the alarm and error status register to one. to enable the receive ais state change interrupt, the receive ais state change interrupt enable bit of the alarm and error interrupt enable register (aeier) have to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive ais state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and ais is present in the incoming ds1 frame, the xrt84l38 framer will declare ais by doing the following: ? set the read-only receive ais state bit of the alarm and error status register (aesr) to one indicating there is ais alarm detected in the incoming ds1 frame. alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 1-0 ais detection select r/w 00 - ais alarm detection is disabled.when this bit is set to 01:detection of unframed ais alarm of all ones pattern is enabled. 10 - ais alarm detection is disabled.when this bit is set to 00:detection of framed ais alarm of all ones pattern except for framing bits is enabled. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 1 receive ais state change interrupt enable r/w 0 - the receive ais state change interrupt is disabled. 1 - the receive ais state change interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled.
xrt84l38 346 octal t1/e1/j1 framer rev. 1.0.1 ? set the receive ais state change bit of the alarm and error status register to one indicating there is a change in state of ais. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive ais state change status bits of the alarm and error status register. the receive ais state bit of the alarm and error status register (aesr), on the other hand, is a read-only bit indicating there is ais alarm detected in the incoming ds1 frame. the table below shows the receive ais state status bits of the alarm and error status register. 10.6.2 how to configure the framer to detect red alarm the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming ds1 frames for red alarm or loss of frame (lof) condition. red alarm condition are detected and declared according to the following procedure: 1. the red alarm is detected by monitoring the occurrence of loss of frame (lof) over a 6 ms interval. 2. an lof valid flag will be posted on the interval when one or more lof occurred during the interval. 3. each interval with a valid lof flag increments a flag counter which declares red alarm when 63 valid intervals have been accumulated. 4. an interval without valid lof flag decrements the flag counter. the red alarm is removed when the counter reaches zero. if lof condition is present in the incoming ds1 frame, the xrt84l38 framer can generate a receive red alarm state change interrupt associated with the setting of receive red alarm state change bit of the alarm and error status register to one. to enable the receive red alarm state change interrupt, the receive red alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 1 receive ais state change rur / wc 0 - there is no change of ais state in the incoming ds1 payload data. 1 - there is change of ais state in the incoming ds1 payload data. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 6 receive ais state r 0 - there is no ais alarm condition detected in the incoming ds1 payload data. 1 - there is ais alarm condition detected in the incoming ds1 payload data.
xrt84l38 347 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the receive red alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and red alarm is present in the incoming ds1 frame, the xrt84l38 framer will declare red alarm by doing the following: ? set the read-only receive red alarm state bit of the alarm and error status register (aesr) to one indicating there is red alarm detected in the incoming ds1 frame. ? set the receive red alarm state change bit of the alarm and error status register to one indicating there is a change in state of red alarm. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive red alarm state change status bits of the alarm and error status register. the receive red alarm state bit of the alarm and error status register (aesr), on the other hand, is a read- only bit indicating there is red alarm detected in the incoming ds1 frame. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 2 receive red alarm state change interrupt enable r/w 0 - the receive red alarm state change interrupt is disabled. no receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. 1 - the receive red alarm state change interrupt is enabled. receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 2 receive red alarm state change rur / wc 0 - there is no change of red alarm state in the incoming ds1 payload data. 1 - there is change of red alarm state in the incoming ds1 payload data.
xrt84l38 348 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the receive red alarm state status bits of the alarm and error status register. 10.6.3 how to configure the framer to detect yellow alarm the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming ds1 frames for yellow alarm condition. the yellow alarm is detected and declared according to the following procedure: 1. monitor the occurrence of yellow alarm pattern over a 6 ms interval. a yel valid flag will be posted on the interval when yellow alarm pattern occurred during the interval. 2. each interval with a valid yel flag increments a flag counter which declares yel alarm when 80 valid intervals have been accumulated. 3. an interval without valid yel flag decrements the flag counter. the yel alarm is removed when the counter reaches zero. if yellow alarm condition is present in the incoming ds1 frame, the xrt84l38 framer can generate a receive yellow alarm state change interrupt associated with the setting of receive yellow alarm state change bit of the alarm and error status register to one. to enable the receive yellow alarm state change interrupt, the receive yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and yellow alarm is present in the incoming ds1 frame, the xrt84l38 framer will declare yellow alarm by doing the following: alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 7 receive red alarm state r 0 - there is no red alarm condition detected in the incoming ds1 payload data. 1 - there is red alarm condition detected in the incoming ds1 payload data. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 0 receive yellow alarm state change interrupt enable r/w 0 - the receive yellow alarm state change interrupt is disabled. any state change of receive yellow alarm will not generate an interrupt. 1 - the receive yellow alarm state change interrupt is enabled. any state change of receive yellow alarm will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled.
xrt84l38 349 rev. 1.0.1 octal t1/e1/j1 framer ? set the read-only receive yellow alarm state bit of the alarm and error status register (aesr) to one indicating there is yellow alarm detected in the incoming ds1 frame. ? set the receive yellow alarm state change bit of the alarm and error status register to one indicating there is a change in state of yellow alarm. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive yellow alarm state change status bits of the alarm and error status register. the table below shows the receive ais state change status bits of the alarm and error status register. the receive yellow alarm state bit of the alarm and error status register (aesr), on the other hand, is a read-only bit indicating there is yellow alarm detected in the incoming ds1 frame. the table below shows the receive yellow alarm state status bits of the alarm and error status register. 10.6.4 how to configure the framer to detect bipolar violation the line coding for the ds1 signal should be bipolar. that is, a binary "0" is transmitted as zero volts while a binary "1" is transmitted as either a positive or negative pulse, opposite in polarity to the previous pulse. a bipolar violation or bpv occurs when the alternate polarity rule is violated. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming ds1 frames for bipolar violations. if a bipolar violation is present in the incoming ds1 frame, the xrt84l38 framer can generate a receive bipolar violation interrupt associated with the setting of receive bipolar violation bit of the alarm and error status register to one. to enable the receive bipolar violation interrupt, the receive bipolar violation interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 0 receive yellow alarm state change rur / wc 0 - there is no change of yellow alarm state in the incoming ds1 payload data. 1 - there is change of yellow alarm state in the incoming ds1 payload data. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 5 receive yellow alarm state r 0 - there is no yellow alarm condition detected in the incoming ds1 pay - load data. 1 - there is yellow alarm condition detected in the incoming ds1 payload data.
xrt84l38 350 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the receive bipolar violation interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and one or more bipolar violations are present in the incoming ds1 frame, the xrt84l38 framer will declare receive bipolar violation by doing the following: ? set the receive bipolar violation bit of the alarm and error status register to one indicating there are one or more bipolar violations. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive bipolar violation status bits of the alarm and error status register. 10.6.5 how to configure the framer to detect loss of signal a loss of signal or los occurs when neither rpos nor rneg inputs of the framer receives a high level input for 32 consecutive bit times. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming ds1 frames for loss of signal conditions. if used in conjunction with exar lius, for example, the xrt83l3x family, the xrt84l38 framer also declares los when the receive los (rxlos) input pin is pulled high. the removal of los condition is through detection of 12.5% ones over 32 consecutive bits. in the other words, xrt84l38 framer will remove los alarm when there is no 4 consecutive zeros received. n ote : the implementation of los detection and removal only apply to b8zs coded bipolar inputs. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 3 receive bipolar violation interrupt enable r/w 0 - the receive bipolar violation interrupt is disabled. occurrence of one or more bipolar violations will not generate an interrupt. 1 - the receive bipolar violation interrupt is enabled. occurrence of one or more bipolar violations will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 3 receive bipolar violation state change rur / wc 0 - there is no change of bipolar violation state in the incoming ds1 pay - load data. 1 - there is change of bipolar violation state in the incoming ds1 payload data.
xrt84l38 351 rev. 1.0.1 octal t1/e1/j1 framer if loss of signal condition is present in the incoming ds1 frame, the xrt84l38 framer can generate a receive loss of signal interrupt associated with the setting of receive loss of signal bit of the alarm and error status register to one. to enable the receive loss of signal interrupt, the receive loss of signal interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive loss of signal interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and one or more loss of signals are present in the incoming ds1 frame, the xrt84l38 framer will declare receive loss of signal by doing the following: ? set the receive loss of signal bit of the alarm and error status register to one indicating there is one or more loss of signals. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive loss of signal status bits of the alarm and error status register. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 4 receive loss of signal interrupt enable r/w 0 - the receive loss of signal interrupt is disabled. occurrence of loss of signals will not generate an interrupt. 1 - the receive loss of signal interrupt is enabled. occurrence of loss of signals will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 4 receive loss of signal state rur / wc 0 - there is no change of loss of signal state in the incoming ds1 payload data. 1 - there is change of loss of signal state in the incoming ds1 payload data.
xrt84l38 352 octal t1/e1/j1 framer rev. 1.0.1 11.0 e1 transmit framer block 11.1 how to configure xrt84l38 to operate in e1 mode the xrt84l38 octal t1/e1/j1 framer supports ds1, j1 or e1 framing modes. since j1 standard is very similar to ds1 standard with a few minor changes, the j1 framing mode is included as a sub-set of the ds1 framing mode. all eight framers within the xrt84l38 silicon can be individually configured to support ds1, j1 or e1 framing modes. n ote : if transmitting section of one framer is configured to support either one of the framing modes, the receiving section is automatically configured to support the same framing modes. the t1/e1 select bit of the clock select register (csr) controls which framing mode, that is, t1/j1 or e1, supported by the framer. the table below illustrates configurations of the t1/e1 select bit of the clock select register (csr). the purpose of the e1 transmit framer block is to embed and encode user payload data into frames and to route this e1 frame data to the transmit e1 liu interface block. please note that the xrt84l38 has eight (8) individual e1 transmit framer blocks. hence, the following description applies to all eight of these individual transmit e1 framer blocks. the purpose of the e1 transmit framer block is: ? to encode user data, inputted from the terminal equipment into a standard framing format. ? to provide individual data control and signaling conditioning of each ds0 channel. ? to support the transmission of hdlc messages, from the local transmitting terminal, to the remote receiving terminal. ? to transmit indications that the local receive framer has received error frames from the remote terminal. ? to transmit alarm condition indicators to the remote terminal. the following sections discuss the functionalities of e1 transmit framer block in detail. we will also describe how to configure the xrt84l38 to transmit e1 frames according to system requirement of users. 11.2 how to configure the framer to transmit and receive data in e1 framing format the xrt84l38 octal t1/e1/j1 framer is designed to meet the requirement of itu-t recommendation g.704. the e1 framer supports the following: ? frame alignment signal (fas) ? crc-4 multi-frame the itu-t recommendation g.704 also specifies two forms of signaling that can be supported by the e1 transport medium: ? channel associated signaling (cas) ? common channel signaling (ccs) the xrt84l38 framer supports both cas, ccs signaling format together with clear channel without signaling. 11.2.1 how to configure the framer to choose fas searching algorithm clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 6 t1/e1 select r/w 0 - the xrt84l38 framer is running in e1 mode. 1 - the xrt84l38 framer is running in t1 mode.
xrt84l38 353 rev. 1.0.1 octal t1/e1/j1 framer the xrt84l38 framer can use two algorithms to search for fas pattern and thus declare fas alignment synchronization. the fas selection bit of the framing select register (fsr) allows the user to choose which one of the two algorithms for searching fas frame alignment. the table below shows configurations of the fas selection bit of the framing select register (fsr). 11.2.2 how to configure the framer to enable crc-4 multi-frame alignment and select the locking criteria the crc-4 selection [1:0] bits of the framing select register (fsr) enable the framer to search for crc-4 multi-frame alignment and select the criteria for locking the crc-4 multi-frame alignment. the table below shows configurations of the crc-4 selection [1:0] bit of the framing select register (fsr). 11.2.3 how to configure the framer to enable cas multi-frame alignment the xrt84l38 framer can use two algorithms to search for cas multi-frame alignment pattern. upon detecting of cas multi-frame alignment pattern, the framer will declare cas multi-frame alignment synchronization and generate the receive cas multi-frame synchronization pulse (rxcasmsync_n). the cas selection [1:0] bits of the framing select register (fsr) enable the framer to search for cas multi-frame alignment. framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 0 fas selection bit r/w this read/write bit field allows the user to determine which algorithm is used for searching fas frame alignment pattern. when an fas alignment pattern is found and locked, the xrt84l38 will generate receive synchro - nization (rxsync_n) pulse. 0 - algorithm 1 is selected for searching fas frame alignment pattern. 1 - algorithm 2 is selected for searching fas frame alignment pattern. framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 3-2 crc-4 selection bit r/w theses read/write bit fields allow the user to enable searching of crc-4 multi-frame alignment and determine what criteria are used for locking the crc-4 multi-frame alignment pattern. 00 - searching of crc-4 multi-frame alignment is disabled. the xrt84l38 framer w ill not search for crc-4 multi-frame alignment and thus will not declare crc-4 multi-frame synchronization. no receive crc-4 multi-frame synchronization (rxcrcmsync_n) pulse will be gener - ated by the framer. 01 - searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if:at least one valid crc-4 multi-frame alignment signal is observed within 8 ms. 10 - searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if:at least two valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 multi-frame alignment signals is multiple of 2 ms. 11 - searching of crc-4 multi-frame alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if:at least three valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 multi-frame alignment signals is multiple of 2 ms.
xrt84l38 354 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the cas selection [1:0] bit of the framing select register (fsr). 11.2.4 how to configure the framer to input the framing alignment bits from different sources in e1 mode, the frame alignment signal (fas) pattern of "0011011" contained in bit 2 to 8 of every other frame (called fas frame) are used to identify the frame boundaries. in addition, bit 2 of the non-fas frames is fixed to "1" to prevent simulation of the fas frames. in the non-fas frames, bit 1 is used to transmit the 6-bit crc-4 multi-frame alignment signal of "001011" and two e bits. the 6-bit crc-4 multi-frame alignment signal is used to identify the crc-4 multi-frame boundaries. the a bit at bit 3 of non-fas frame is used as remote yellow alarm indication. when the a bit is "0", it denotes undistributed operation of the framer. when the a bit is "1", it denotes yellow alarm condition. the framing alignment bits include the fas pattern, the crc-4 multi-frame alignment bits and the a bit. under default condition, the xrt84l38 can generate these framing alignment bits internally. at the same time, the users can generate the framing alignment bits externally and insert them into the framer through the transmit serial data input interface block via the txser_n pin. it is the user's responsibility to maintain the accuracy and integrity of the framing alignment bits. the user also has to make sure that the framing alignment bits are inserted into the framer at right position and right timing. however, this option is only available when the xrt84l38 is configured to run at a normal back-plane rate of 2.048mbit/s in e1 mode. the framing bit source select bit of the synchronization mux register (smr) controls source of the framing alignment bit. the table below shows configurations of the framing bit source select bit of the synchronization mux register (smr). framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 5-4 cas selection bit r/w these read/write bit fields allow the user to enable searching of cas multi-frame alignment and determine which algorithm of the two are used for locking the cas multi-frame alignment pattern. 00 - searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. 01 - searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchronization using algo - rithm 1. 10 - searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchronization using algo - rithm 2 (g.732). 11 - searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 0 framing bit source r/w this read/write bit-field permits the user to determine where the fram - ing alignment bits should be inserted. 0 - the framing alignment bits are generated and inserted by the framer internally. 1 - if the framer is operating in normal 2.048mbit/s mode, the framing align - ment bits are passed through from the transmit serial data input interface block via the txser_n pin.
xrt84l38 355 rev. 1.0.1 octal t1/e1/j1 framer 11.2.5 how to configure the framer to input crc-4 bits from different sources each e1 crc-4 multi-frame is divided into two sub-multi-frames. each sub-multi-frame consists of 8 e1 frames. if the framer is configured to operate in crc-4 multi-frame format, bit 1 of the fas frames are used as cyclic redundancy check (crc-4) code of the last crc-4 sub- multi-frame. the crc-4 bits are an indicator of the link quality and could be monitored by the user to establish error performance report. the xrt84l38 can generate the crc-4 bits internally by calculating the crc check-sum of all the payload bits in each e1 sub-multi-frame. at the same time, the users can generate the crc-4 bits ex ternally and insert them into the framer through the transmit serial data input interface block via the txser_n pin. it is the user's responsibility to correctly compute the crc-4 bits according to e1 algorithm. also, the user has to make sure that the crc-4 bits are inserted into the framer at right position and right timing. however, this option is only available when the xrt84l38 is configured to run at a normal back-plane rate of 2.048mbit/s. the crc-4 source select bit of the synchronization mu x register (smr) controls from where to input crc-4 bits into the framer. the table below shows configurations of the crc-4 source select bit of the synchronization mux register (smr). 11.2.6 how to configure the framer to input e bits from different sources each e1 crc-4 multi-frame is divided into two sub-multi-frames. each sub-multi-frame consists of 8 e1 frames, 4 of them are fas frames and the other 4 are non-fas frames. of the seco nd crc-4 sub-multi-frame, bit 1 of the last 2 non-fas frames is called e bit. the e bits are used to indicate that the previous received sub-multi-frame is error-ed. when a sub-multi-frame is received, the framer calculated the crc-4 bits of th e received sub-multi-frame. the frame then compares the calculated crc-4 bits with the received crc-4 bits. if they are the same, the framer will set e bit to "1" and transmit it to the remote terminal. if the calculated crc-4 bits and the receive crc-4 bits are different, the framer will set e bit to "0" and transmit it out. the first e bit indicates error of the first crc-4 sub-multi-frame while the second e bit indicates error of the second crc-4 sub-multi-frame. the delay between the detection of an error-ed crc-4 sub-multi-frame and the setting of the corresponding e bit that represents the error state should not be more than one second. if the e bits are not used, they should be set to "1". n ote : the e bits will always be taken into account even if the sub-multi-frame which contains them is error-ed. under default condition, the xrt84l38 generate the e bits internally by calculating the crc check-sum of all the payload bits in each received e1 sub-multi-frame and compare them against the received crc-4 bits. at the same time, the users can force the e bits to either "0" or "1". source of the e bits can also be the internal hdlc controller such that the e bits can be used to transmit data link message. synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 1 crc-4 source select r/w this read/write bit-field permits the user to determine where the crc- 4 bits should be inserted. 0 - the crc-4 bits are g enerated and inserted by the framer internally. 1 - if the framer is operating in normal 2.048mbit/s mode, the crc-4 bits are generated by external equipment and passed through from the trans - mit serial data input interface block via the txser_n pin.
xrt84l38 356 octal t1/e1/j1 framer rev. 1.0.1 the e bit source select bit of the synchronization mux register (smr) controls from where to input e bits into the framer. the table below shows configurations of the e bit source select bit of the synchronization mux register (smr). 11.3 how to configure the framer to apply data and signaling conditioning to e1 payload data on a per-channel basis the xrt84l38 t1/j1/e1 octal framer provides individual control of each of the thirty two ds0 channels. the user can apply data and signaling conditioning to raw e1 payload data coming from the terminal equipment on a per-channel basis. the xrt84l38 framer can apply the following changes to raw e1 pcm data coming from the terminal equipment on a per-channel basis: ? all 8 bits of the input pcm data are inverted ? the even bits of the input pcm data are inverted ? the odd bits of the input pcm data are inverted ? the msb of the input pcm data is inverted ? all input pcm data except the msb are inverted configuration of the xrt84l38 framer to apply the above-mentioned changes to raw e1 pcm data are controlled by the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each ds0 channel. the xrt84l38 framer can also replace the incoming raw e1 pcm data from the terminal equipment with pre- defined or user-defined codes. the xrt84l38 supports the following conditioning substitutions: ? busy code - an octet with hexadecimal value of 0x7f ? busy_ts code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number ? vacant code - an octet with hexadecimal value of 0xff ? a-law digital milliwatt code ? u-law digital milliwatt code ? idle code - an octet defined by the value stored in the user idle code register (ucr) ? moof code - mux-out-of-frame code with hexadecimal value of 0x1a ? prbs code - an octet generated by the pseudo-random bit sequence (prbs) generator block of the framer synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 7-6 e bit source select r/w these read/write bit-fields permits the user to determine where the e bits should be inserted and what the e bits should be. 00 - the e bits are generated and inserted by the framer internally. 01 - the e bits are forced to be "0" and are inserted by the framer inter - nally. 10 - the e bits are forced to be "1" and are inserted by the framer inter - nally. 11 - source of the e bits is hdlc controller of the framer. the e bits are used to carry data link messages.
xrt84l38 357 rev. 1.0.1 octal t1/e1/j1 framer once again, configuration of the xrt84l38 framer to replace raw e1 pcm data with the above-mentioned coding schemes are controlled by the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each ds0 channel. finally, the xrt84l38 framer can configure any one or ones of the thirty two ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each channel determine whether that particular channel is configured as d or e channel. the table below illustrates configurations of the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr). transmit channel control register (tccr) (indirect address = 0xn2h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 3-0 transmit conditioning select r/w 0000 - the input e1 pcm data of this ds0 channel is unchanged. 0001 - all 8 bits of the input e1 pcm data of this ds0 channel are inverted. 0010 - the even bits of the input e1 pcm data of this ds0 channel are inverted. 0011 - the odd bits of the input e1 pcm data of this ds0 channel are inverted. 0100 - the input e1 pcm data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). 0101 - the input e1 pcm data of this ds0 channel are replaced by busy code (0x7f). 0110 - the input e1 pcm data of this ds0 channel are replaced by vacant code (0xff). 0111 - the input e1 pcm data of this ds0 channel are replaced by busy_ts code (111xxxxx). 1000 - the input e1 pcm data of this ds0 channel are replaced by mux- out-of-frame (moof) code with value 0x1a. 1001 - the input e1 pcm data of this ds0 channel are replaced by the a- law digital milliwatt pattern. 1010 - the input e1 pcm data of this ds0 channel are replaced by the u- law digital milliwatt pattern. 1011 - the msb bit of the input e1 pcm data of this ds0 channel is inverted. 1100 - all bits of the input e1 pcm data of this ds0 channel except msb bit are inverted. 1101 - the input e1 pcm data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. 1110 - the input e1 pcm data of this ds0 channel is unchanged. 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 358 octal t1/e1/j1 framer rev. 1.0.1 when the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of a particular ds0 channel are set to 0100, input e1 pcm data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). the table below shows contents of the user idle code register. 11.4 how to configure the xrt84l38 framer to transmit signaling information each 256-bit e1 frame is divided into 32 octets or time slots numbered 0 to 31. each time slot is a 64kbits/s channel carrying voice or data information. the time slot 0 is used for frame and multi-frame synchronization, crc-4 error detection, yellow alarm transmission and data link transmission. the time slot 1 to time slot 15 and time slot 17 to time slot 31 are used to carry a pcm encoded voice band signal or data. the remaining 64kbits/s channel time slot 16 may be used for signaling. the xrt84l38 t1/j1/e1 octal framer supports the following signaling formats to interconnect to cept channelized service functions: ? common channel signaling (ccs) ? channel associated signaling (cas) ? primary rate isdn message oriented signaling (isdn-pri) the xrt84l38 t1/j1/e1 octal framer supports insertion of various types of signaling information into the timeslot 16 of an outgoing e1 frame. it also supports extraction and substitution of signaling information from the incoming e1 frame. the following section provides a brief overview of common channel signaling, channel associated signaling in e1 mode. n ote : the time slot 16 can also be configured to carry pcm encoded voice or data if neither ccs nor cas signaling is used. the xrt84l38 framer allows the user to choose which one of the ccs, cas, isdn-pri message or pcm data to be carries on the time slot 16. 11.4.1 brief discussion of common channel signaling in e1 framing format as the name referred, common channel signaling is signaling information common to all thirty voice or data channels of an e1 trunk. the time slot 16 may be used to carry common channel signaling data of up to a rate of 64kbits/s. the national bits of time slot 0 may also be used for common channel signaling. since there are five national bits of time slot 0 per every two e1 frames, the total bandwidth of the national bits is 20kbits/s. the common channel signaling is essentially data link information that provides performance monitoring and transmission quality report. 11.4.2 brief discussion of channel associated signaling in e1 framing format signaling is required when dealing with voice and dial-up data services in e1 applications. traditionally, signaling is provided on a dial-up telephone line, across the talk-path. signaling is used to tell the receiver where the call or route is destined. the signal is sent through switches along the route to a distant end. common types of signals are: ? on hook ? off hook ? dial tone ? dialed digits ? ringing cycle user idle code register (ucr) (indirect address = 0xn02h, 0x20h - 0x3fh) b it n umber b it n ame b it t ype b it d escription 7-0 user idle code r/w these read/write bit-fields permits the user store any value of idle code into the framer. when the transmit data conditioning select [3:0] bits of tccr register of a particular ds0 channel are set to 0100, the input e1 pcm data are replaced by contents of this register and sent to the trans - mit liu interface.
xrt84l38 359 rev. 1.0.1 octal t1/e1/j1 framer ? busy tone a signal is consists of four bits namely a, b, c and d. these bits define the state of the call for a particular time slot. the time slot 16 octet of each e1 frame can carry cas signals for two e1 voice or data channels. therefore, sixteen e1 frames are needed to carry cas signals for all 32 e1 channels. the sixteen e1 frames then forms a cas multi-frame. the time slot 16 of frame number 0 of an e1 cas multi-frame carries the pattern of "0000 xyxx". the time slot 16 of frame number 1 carries signals of channel 1 and channel 17. the time slot 16 of frame number 2 carries signals of channel 2 and channel 18, and so on. the following table shows the bit allocations of channel associated signaling in e1 framing format. the four zeros pattern is the multi-frame alignment signal that indicates the beginning of an e1 cas multi- frame. the xrt84l38 framer, upon detection of the four zeros pattern in the time slot 16, declares cas multi- frame synchronization and would pulse the receive cas multi-frame synchronization pulse (rxcasmsync_n) high for one clock period. the user, triggering on the receive cas multi-frame synchronization pulse, would thus identify the received cas multi-frame boundary. the x in xyxx pattern located in the time slot 16 of frame number 0 should be fixed to "1" and can be used to prevent mimicking of cas multi-frame alignment pattern. the y in xyxx pattern is used for alarm indication of time slot 16 to the remote terminal. if signals of time slot 16 is transmitted and received correctly, the y bit is set to "0". in an alarm condition, the y bit is set to "1". therefore, y bit is also known as cas multi-frame yellow alarm. 11.4.3 configure the framer to transmit channel associated signaling the xrt84l38 framer supports transmission of common channel signaling and channel associated signaling according to itu-t recommendation g.704. as discussed briefly before, channel associated signaling includes the signaling bits, the cas multi-frame alignment pattern and the x and y bits. signaling bits can be inserted into the outgoing e1 frame through the following: t ime slot 16 of f rame 0 t ime slot 16 of f rame 1 t ime slot 16 of f rame 2 t ime slot 16 of f rame 3 0000 xyxx abcd of ch. 1 abcd of ch. 17 abcd of ch. 2 abcd of ch. 18 abcd of ch. 3 abcd of ch. 19 t ime slot 16 of f rame 4 t ime slot 16 of f rame 5 t ime slot 16 of f rame 6 t ime slot 16 of f rame 7 abcd of ch. 4 abcd of ch. 20 abcd of ch. 5 abcd of ch. 21 abcd of ch. 6 abcd of ch. 22 abcd of ch. 7 abcd of ch. 23 t ime slot 16 of f rame 8 t ime slot 16 of f rame 9 t ime slot 16 of f rame 10 t ime slot 16 of f rame 11 abcd of ch. 8 abcd of ch. 24 abcd of ch. 9 abcd of ch. 25 abcd of ch. 10 abcd of ch. 26 abcd of ch. 11 abcd of ch. 27 t ime slot 16 of f rame 12 t ime slot 16 of f rame 13 t ime slot 16 of f rame 14 t ime slot 16 of f rame 15 abcd of ch. 12 abcd of ch. 28 abcd of ch. 13 abcd of ch. 29 abcd of ch. 14 abcd of ch. 30 abcd of ch. 15 abcd of ch. 31
xrt84l38 360 octal t1/e1/j1 framer rev. 1.0.1 ? signaling data is inserted from the transmit signaling control registers (tscr) of each timeslot. ? signaling data is inserted from txsig_n pin. ? signaling data is inserted from txoh-n pin. ? signaling data is embedded into the input pcm data coming from the terminal equipment. the cas multi-frame alignment pattern of four zeros can be inserted into the outgoing e1 frame by using the following method: ? cas multi-frame alignment pattern is inserted from thetransmit signaling control registers (tscr). ? cas multi-frame alignment pattern is inserted from txsig_n pin. ? cas multi-frame alignment pattern is inserted from txoh-n pin. ? cas multi-frame alignment pattern is embedded into the input pcm data coming from the terminal equipment. the cas multi-frame yellow alarm y bit and the x bits can be inserted into the outgoing e1 frame by using the following method: ? the x and y bits are inserted from the transmit signaling control register (tscr). ? the x and y bits are inserted from txsig_n pin. ? the x and y bits are inserted from txoh-n pin. ? the x and y bits are embedded into the input pcm data coming from the terminal equipment. ? the x bit is inserted from the transmit signaling control register (tscr) and y bit is generated by the xrt84l38 framer according to operating condition of the e1 link. 11.4.3.1 insert signaling bits from tscr register the four most significant bits of the transmit signaling control register (tscr) of each time slot can be used to store outgoing signaling data. the user can program these bits through microprocessor access. if the xrt84l38 framer is configure to insert signaling bits from tscr registers, the e1 transmit framer block will fill up the time slot 16 octet with the signaling bits stored inside the tscr registers. the insertion of signaling bit into pcm data is done on a per-channel basis. the most significant bit (bit 7) of tscr register is used to store signaling bit a. bit 6 is used to hold signaling bit b. bit 5 is used to hold signaling bit c. bit 4 is used to hold signaling bit d. the table below shows the four most significant bits of the transmit signaling control register. 11.4.3.2 insert signaling bits from txsig_n pin the xrt84l38 framer can be configure to insert signaling bits provided by external equipment through the txsig_n pins. this pin is a multiplexed i/o pin with two functions: ? txtsb[0]_n - transmit timeslot number bit [0] output pin ? txsig_n - transmit signaling input pin transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x5fh) b it n umber b it n ame b it t ype b it d escription 7 signaling bit a r/w this bit is used to store signaling bit a. 6 signaling bit b r/w this bit is used to store signaling bit b. 5 signaling bit c r/w this bit is used to store signaling bit c. 4 signaling bit d r/w this bit is used to store signaling bit d.
xrt84l38 361 rev. 1.0.1 octal t1/e1/j1 framer when the transmit fractional e1 bit of the transmit interface control register (ticr) is set to 0, this pin is configured as txtsb[0]_n pin, it outputs bit 0 of the timeslot number of the e1 pcm data that is transmitting. when the transmit fractional e1 bit of the transmit interface control register (ticr) is set to 1, this pin is configured as txsig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound e1 frames. figure 117 below is a timing diagram of the txsig_n input pin. please note that the signaling bit a of a certain channel coincides with bit 5 of the pcm data of that channel; signaling bit b coincides with bit 6 of the pcm data; signaling bit c coincides with bit 7 of the pcm data and signaling bit d coincides with bit 8 (lsb) of the pcm data. the table below shows configurations of the transmit fractional e1 bit of the transmit interface control register (ticr). 11.4.3.3 insert signaling bits from txoh_n pin the xrt84l38 framer can be configure to insert signaling bits provided by external equipment through the transmit overhead txoh_n input pins. the txoh_n pin can acts as an input source for the signaling bits to be transmitted in the outbound e1 frames. when this pin is chosen as the input source for the signaling bits, any data presents on this pin in time slot 16 would be taken into the framer directly. the time slot 16 octet of the outbound e1 frame will be replaced by data inputted from this pin in time slot 16. please note that the signaling bit a of channel 1-15 coincides with bit 1 of the pcm data; signaling bit b channel 1-15 coincides with bit 2 of the pcm data; signaling bit c channel 1-15 coincides with bit 3 of the pcm; signaling bit d channel 1-15 coincides with bit 4 of the pcm data. similarly, the signaling bit a of channel 17-31 coincides with bit 5 of the pcm data; signaling bit b channel 17-31 coincides with bit 6 of the pcm data; signaling bit c channel 17-31 coincides with bit 7 of the pcm; signaling bit d channel 17-31 coincides with bit 8 of the pcm data. f igure 117. t iming d iagram of the t x s ig _ n i nput transmit interface control register (ticr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 transmit fractional e1 r/w this read/write bit-field permits the user to determine which one of the two functions the multiplexed i/o pin of txtsb[0]_n/txsig_n is spotting. 0 - this pin is configured as txtsb[0]_n pin, it outputs bit 0 of the timeslot number of the e1 pcm data that is transmitting. 1 - this pin is configured as txsig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound e1 frames txserclk txserclk (inv) txser f f input data input data input data input data timeslot 23 timeslot 0 timeslot 5 timeslot 6 c txsig a b d c a b d c a b d c a b d
xrt84l38 362 octal t1/e1/j1 framer rev. 1.0.1 figure 118 below is a timing diagram of the txoh_n input pin. 11.4.3.4 insert signaling data from txser_n pin depends on applications, the terminal equipment can embed signaling information into the e1 pcm data and then send the data to the xrt84l38 framer device. in this case, the user should configure the framer not to insert any signaling data. the input e1 pcm data will then be directed to the transmit liu interface without any modifications. 11.4.3.5 enable channel associated signaling and signaling data source control the transmit signaling control register (tscr) of each channel selects source of signaling data to be inserted into the outgoing e1 frame and enables channel associated signaling. as we mentioned before, the signaling data can be inserted from transmit signaling control registers (tscr) of each timeslot, from the txsig_n input pin, from the txoh_n input pin or from the txser_n input pin. the transmit signaling data source select [1:0] bits of the transmit signaling control register (tscr) determines from which sources the signaling data is inserted from. the table below shows configurations of the transmit signaling data source select [1:0] bits of the transmit signaling control register (tscr). f igure 118. t iming d iagram of the t x oh_ n i nput transmit signaling control register (tscr) (indirect address = 0xn2h, 0x40h - 0x57h) b it n umber b it n ame b it t ype b it d escription 1-0 transmit signaling source select r/w 00 - none of the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgo - ing e1 pcm data by the framer. however, the user can embed the signal - ing data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y into e1 pcm data before routing the pcm data into the framer. 01 - the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from tscr register of each timeslot. 10 - if the xrt84l38 framer is operating in e1 2.048mbit/s mode and if the txfr2048 bit of the transmit interface control register (ticr) is set to zero: the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from the txoh_n input pin. if the xrt84l38 framer is operating in e1 2.048mbit/s mode and if the txfr2048 bit of the transmit interface control register (ticr) is set to one: the signaling data, the cas multi-frame alignment pattern, the x bit or the cas multi-frame yellow alarm bit y is inserted into the outgoing e1 pcm data from the txsig_n input pin. 11 - no signaling data or the cas multi-frame alignment pattern is inserted into the input e1 pcm data by the framer. however, the user can embed signaling data into e1 pcm data before routing the pcm data into the framer. the x bit is inserted into the outgoing e1 pcm data from tscr register. the cas multi-frame yellow alarm y bit is generated by the xrt84l38 framer depends on operating condition of the e1 link.
xrt84l38 363 rev. 1.0.1 octal t1/e1/j1 framer 11.5 how to configure the xrt84l38 framer to generate and transmit alarms and error indications to remote terminal the xrt84l38 t1/j1/e1 octal framer can be configured to monitor quality of received e1 frames. it can generate error indications if the local receive framer has received error frames from the remote terminal. if corresponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. upon microprocessor interruption, the user can intervene by looking into the error conditions. at the same time, the user can configure the xrt84l38 framer to transmit alarms and error indications to remote terminal. different alarms and error indications will be transmitted depending on the error condition. the section below gives a brief discussion of the error conditions and appropriate alarms that should be generated and transmitted by the xrt84l38 framer. 11.5.1 brief discussion of alarms and error conditions as defined in e1 specification, alarm conditions are created from defects. defects are momentary impairments present on the e1 trunk. if a defect is present for a sufficient amount of time (called the integration time), then the defect becomes an alarm. once an alarm is declared, the alarm is present until after the defect clears for a sufficient period of time. the time it takes to clear an alarm is called the de-integration time. alarms are used to detect and warn maintenance personnel of problems on the e1 trunk. there are three types of alarms: ? red alarm or service alarm indication (sai) signal ? blue alarm or alarm indication signal (ais) ? yellow alarm or remote alarm indication (rai) signal to explain the error conditions and generation of different alarms, let us create a simple e1 system model. in this model, an e1 signal is sourced from the central office (co) through a repeater to the customer premises equipment (cpe). at the same time, an e1 signal is routed from the cpe to the repeater and back to the central office. figure 119 below shows the simple e1 system model. when the e1 system runs normally, that is, when there is no loss of signal (los) or loss of frame (lof) detected in the line, no alarm will be generated. sometimes, intermittent outburst of electrical noises on the line might result in bipolar violation or bit errors in the incoming signals, but these errors in general will not trigger f igure 119. s imple d iagram of e1 system model e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe simple e1 system model
xrt84l38 364 octal t1/e1/j1 framer rev. 1.0.1 the equipment to generate alarms. they will, depending on the system requ irements, trigger the framer to generate interrupts that would cause the local microprocessor to create performance reports of the line. now, consider a case in which the e1 line from the co to the repeater is broken or interrupted, resulting in completely loss of incoming data or severely impaired signal quality. upon detection of loss of signal (los) or loss of frame (lof) condition, the repeater will generate an internal red alarm, also known as the service alarm indication. this alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. when the repeater is in the red alarm state, it will transmit the yellow alarm to the co indicating the loss of an incoming signal or loss of frame synchronization. this yellow alarm informs the repeater that there is a problem further down the line and its transmission is not being received at the repeater. figure 120 below illustrates the scenario in which the e1 connection from the co to the repeater is broken. the repeater will also transmit a blue alarm, also known as alarm indication signal (ais) to the cpe. blue alarm is an all ones pattern indicating that the equipment is functioning but unable to offer service due to failures originated from remote side. it is sent such that the equipment downstream will not lose clock f igure 120. g eneration of y ellow a larm by the r epeater upon detection of line failure e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe the e1 line is broken repeater declares red alarm internally yellow alarm repeater generates yellow alarm to co
xrt84l38 365 rev. 1.0.1 octal t1/e1/j1 framer synchronization even though no meaningful data is received. figure 121 below illustrates this scenario in which the repeater is sending an ais to the cpe upon detection of line failure from the co. now, the cpe uses the ais signal sent by the repeater to recover received clock and remain in synchronization with the system. upon detecting the incoming ais signal, the cpe will generate a yellow alarm automatically to the repeater to indicate the loss of incoming data. figure 122 below illustrates this scenario in which the repeater is sending an ais to the cpe and the cpe is sending a yellow alarm back to the repeater. f igure 121. g eneration of ais by the r epeater upon detection of line failure e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe the e1 line is broken repeater declares red alarm internally yellow alarm repeater generates yellow alarm to co repeater generates ais to cpe ais
xrt84l38 366 octal t1/e1/j1 framer rev. 1.0.1 next, let us consider the scenario in which the signaling and data link channel (the time slot 16) of an e1 line between a far-end terminal (for example, the co) and a near-end terminal (for example, the repeater) is impaired. in this case, the cas signaling data received by the repeater is corrupted. the repeater will then send an all ones pattern in time slot 16 (ais16 pattern) downstream to the cpe. the repeater will also generate a cas multi-frame yellow alarm upstream to the co to indicate the loss of cas multi-frame f igure 122. g eneration of y ellow a larm by the cpe upon detection of ais originated by the r epeater e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe the e1 line is broken repeater declares red alarm internally yellow alarm repeater generates yellow alarm to co repeater generates ais to cpe ais yellow alarm cpe detects ais and generates yellow alarm to repeater
xrt84l38 367 rev. 1.0.1 octal t1/e1/j1 framer synchronization. figure 123 below illustrates this scenario in which the repeater is sending an "ais16" pattern to the cpe while sending a cas multi-frame yellow alarm to the co. f igure 123. g eneration of cas m ulti - frame y ellow a larm and ais16 by the r epeater e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe the timeslot 16 of an e1 line is iimpaired repeater generates cas multi-frame yellow alarm to co repeater generates ais16 to cpe ais16 cas multi- frame yellow alarm
xrt84l38 368 octal t1/e1/j1 framer rev. 1.0.1 the cpe, upon detecting the incoming ais16 signal, will generate a cas multi-frame yellow alarm to the repeater to indicate the loss of cas multi-frame synchronization. figure 124 below illustrates the cpe sending a cas multi-frame yellow alarm back to the repeater in summary, ais or blue alarm is sent by a piece of e1 equipment downstream indicating that the incoming signal from upstream is lost. yellow alarm is sent by a piece of e1 equipment upstream upon detection of loss of signal, loss of frame or when it is receiving ais. similarly, an "ais16" pattern is sent by a piece of e1 equipment downstream indicating that the incoming data link channel from upstream is damaged. the cas multi-frame yellow alarm is sent by a piece of e1 equipment upstream upon detection of loss of cas multi-frame synchronization or when it is receiving an "ais16" pattern. 11.5.2 how to configure the framer to transmit ais as we discussed in the previous section, alarm indication signal (ais) or blue alarm is transmitted by the intermediate node to indicate that the equipment is still functioning but unable to offer services. it is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. the xrt84l38 framer can generate three types of ais when it is running in e1 format: ? framed ais ? unframed ais ? ais16 unframed ais is an all ones pattern. if unframed ais is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received ais signal. however, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare loss of frame (lof). f igure 124. g eneration of cas m ulti - fram y ellow a larm by the cpe upon detection of ?ais16? pat - tern sent by the r epeater e1 receive framer block e1 transmit framer block e1 receive framer block e1 transmit framer block e1 transmit section e1 transmit section e1 receive section e1 receive section co repeater cpe the timeslot 16 of an e1 line is iimpaired repeater generates cas multi-frame yellow alarm to co repeater generates ais16 to cpe ais16 cas multi- frame yellow alarm cpe detects ais16 and generates cas multi-frame yellow alarm to repeater cas multi- frame yellow alarm
xrt84l38 369 rev. 1.0.1 octal t1/e1/j1 framer on the other hand, the payload portion of a framed ais pattern is all ones. however, a framed ais pattern still has correct framing bits. therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. in this case, no lof or red alarm will be declared. "ais16" is an ais alarm that only supported in e1 framing format. it is an all ones pattern in time slot 16 of each e1 frame. as we mentioned before, time slot 16 is usually used for signaling and data link in e1, therefore, an "ais16" alarm is transmitted by the intermediate node to indicate that the data link channel is having a problem. since all the other thirty one time slots are still transmitting normal data (that is, framing information and pcm data), therefore, the equipment further down the line can still maintain frame synchronization, timing synchronization as well as receiving pcm data. in this case, no lof or red alarm will be declared by the equipments further down the line. however, a cas multi-frame yellow alarm will be sent by the equipment further down the line to indicate the loss of cas multi-frame alignment. the transmit alarm indication signal select [1:0] bits of the alarm generation register (agr) enable the three types of ais transmission that are supported by the xrt84l38 framer. the table below shows configurations of the transmit alarm indication signal select [1:0] bits of the alarm generation register (agr). 11.5.3 how to configure the framer to generate red alarm upon detection of loss of signal (los) or loss of frame (lof) condition, the repeater will generate an internal red alarm when enabled. this alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. the loss of frame declaration enable bit of the alarm generation register (agr) enable the generation of red alarm. the table below shows configurations of the of frame declaration enable bit of the alarm generation register (agr). 11.5.4 how to configure the framer to transmit yellow alarm the xrt84l38 framer supports transmission of both yellow alarm and cas multi-frame yellow alarm in e1 mode. alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 3-2 transmit ais select r/w these read/write bit-fields allows the user to choose which one of the three ais pattern supported by the xrt84l38 framer will be transmitted. 00 - no ais alarm is generated. 01 - enable unframed ais alarm of all ones pattern. 11 - ais16 pattern is generated. only time slot 16 is carrying the all ones pattern. the other time slots still carry framing and pcm data. 11 - enable framed ais alarm of all ones pattern except for framing bits. alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 6 loss of frame declaration enable r/w this read/write bit-field permits the framer to declare red alarm in case of loss of frame alignment (lof). when receiver module of the framer detects loss of frame alignment in the incoming data stream, it will generate a red alarm. the framer will also generate an rxlofs interrupt to notify the microprocessor that an lof condition is occurred. a yellow alarm is then returned to the remote transmitter to report that the local receiver detects lof. 0 - red alarm declaration is disabled. 1 - red alarm declaration is enabled.
xrt84l38 370 octal t1/e1/j1 framer rev. 1.0.1 upon detection of loss of signal (los) or loss of frame (lof) condition, the receiver will transmit the yellow alarm back to the source indicating the loss of an incoming signal. this yellow alarm informs the source that there is a problem further down the line and its transmission is not being received at the destination. on the other hand, upon detection of loss of cas multi-frame alignment pattern, the receiver section of the xrt84l38 framer will transmit a cas multi-frame yellow alarm back to the source indicating the loss of cas multi-frame synchronization. the yellow alarm generation select [1:0] bits of the alarm generation register (agr) enable transmission of different types of yellow alarm that are supported by the xrt84l38 framer. 11.5.4.1 transmit yellow alarm the yellow alarm bits are located at bit 3 of time slot 0 of non-fas frames. a logic one of this bit denotes the yellow alarm and a logic zero of this bit denotes normal operation. the xrt84l38 supports transmission of yellow alarm automatically or manually. when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 01, the yellow alarm bit is transmitted by echoing the received fas alignment pattern. if the correct fas alignment is received, the yellow alarm bit is set to zero. if the fas alignment pattern is missing or corrupted, the yellow alarm bit is set to one while loss of frame synchronization is declared. when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 10, the yellow alarm bit is transmitted as zero. when the yellow alarm generation select [1:0] bits of the alarm generation register are set to 11, the yellow alarm bit is transmitted as one. 11.5.4.2 transmit cas multi-frame yellow alarm within the sixteen-frame cas multi-frame, the cas multi-frame yellow alarm bits are located at bit 6 of time slot 16 of frame number 0. a logic one of this bit denotes the cas multi-frame yellow alarm and a logic zero of this bit denotes normal operation. the xrt84l38 supports transmission of cas multi-frame yellow alarm automatically or manually. when the cas multi-frame yellow alarm generation select [1:0] bits of the alarm generation register are set to 01, the cas multi-frame yellow alarm bit is transmitted by echoing the received cas multi-frame alignment pattern (the four zeros pattern). if the correct cas multi-frame alignment is received, the cas multi-frame yellow alarm bit is set to zero. if the cas multi-frame alignment pattern is missing or corrupted, the cas multi- frame yellow alarm bit is set to one while loss of cas multi-frame synchronization is declared. when the cas multi-frame yellow alarm generation select [1:0] bits of the alarm generation register are set to 10, the cas multi-frame yellow alarm bit is transmitted as zero. when the cas multi-frame yellow alarm generation select [1:0] bits of the alarm generation register are set to 11, the cas multi-frame yellow alarm bit is transmitted as one.
xrt84l38 371 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the yellow alarm generation select [1:0] bits of the alarm generation register (agr). alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 5-4 ye ll ow a la r m g e n - eration select r/w these read/write bit-fields allows the user to choose how the xrt84l38 would generate yellow alarm and cas multi-frame yellow alarm. 00 - transmission of yellow alarm and cas multi-frame yellow alarm is disabled. 01 - the yellow alarm bit is transmitted by echoing the received fas align - ment pattern. if the correct fas alignment is received, the yellow alarm bit is set to zero. if the fas alignment pattern is missing or corrupted, the yel - low alarm bit is set to one. the cas multi-frame yellow alarm bit is transmitted by echoing the received cas multi-frame alignment pattern (the four zeros pattern). if the correct cas multi-frame alignment is received, the cas multi-frame yellow alarm bit is set to zero. if the cas multi-frame alignment pattern is missing or corrupted, the cas multi-frame yellow alarm bit is set to one. 10 - the yellow alarm and cas multi-frame yellow alarms are transmitted as zero. 11 - the yellow alarm and cas multi-frame yellow alarms are transmitted as one.
xrt84l38 372 octal t1/e1/j1 framer rev. 1.0.1 12.0 e1 receive framer block 12.1 how to configure xrt84l38 to operate in e1 mode the xrt84l38 octal t1/e1/j1 framer supports ds1, j1 or e1 framing modes. since j1 standard is very similar to ds1 standard with a few minor changes, the j1 framing mode is included as a sub-set of the ds1 framing mode. all eight framers within the xrt84l38 silicon can be individually configured to support ds1, j1 or e1 framing modes. n ote : if transmitting section of one framer is configured to support either one of the framing modes, the receiving section is automatically configured to support the same framing modes. the t1/e1 select bit of the clock select register (csr) controls which framing mode, that is, t1/j1 or e1, supported by the framer. the table below illustrates configurations of the t1/e1 select bit of the clock select register (csr). the purpose of the e1 transmit framer block is to embed and encode user payload data into frames and to route this e1 frame data to the transmit e1 liu interface block. please note that the xrt84l38 has eight (8) individual e1 transmit framer blocks. hence, the following description applies to all eight of these individual transmit e1 framer blocks. the purpose of the e1 transmit framer block is: ? to encode user data, inputted from the terminal equipment into a standard framing format. ? to provide individual data control and signaling conditioning of each ds0 channel. ? to support the transmission of hdlc messages, from the local transmitting terminal, to the remote receiving terminal. ? to transmit indications that the local receive framer has received error frames from the remote terminal. ? to transmit alarm condition indicators to the remote terminal. the following sections discuss the functionalities of e1 transmit framer block in details. we will also describe how to configure the xrt84l38 to transmit e1 frames according to system requirement of users. 12.2 how to configure the framer to receive data in various e1 framing formats the xrt84l38 octal t1/e1/j1 framer is designed to meet the requirement of itu-t recommendation g.704. the e1 framer supports the following: ? frame alignment signal (fas) ? crc-4 multi-frame the itu-t recommendation g.704 also specifies two forms of signaling that can be supported by the e1 transport medium: ? channel associated signaling (cas) ? common channel signaling (ccs) the xrt84l38 framer supports both cas, ccs signaling format together with clear channel without signaling. 12.2.1 how to configure the framer to choose fas searching algorithm clock select register (csr) (indirect address = 0xn0h, 0x00h) b it n umber b it n ame b it t ype b it d escription 6 t1/e1 select r/w 0 - the xrt84l38 framer is running in e1 mode. 1 - the xrt84l38 framer is running in t1 mode.
xrt84l38 373 rev. 1.0.1 octal t1/e1/j1 framer the xrt84l38 framer can use two algorithms to search for fas pattern and thus declare fas alignment synchronization. the fas selection bit of the framing select register (fsr) allows the user to choose which one of the two algorithms for searching fas frame alignment. the table below shows configurations of the fas selection bit of the framing select register (fsr). 12.2.2 how to configure the framer to enable crc-4 multi-frame alignment and select the locking criteria the crc-4 selection [1:0] bits of the framing select register (fsr) enable the framer to search for crc-4 multi-frame alignment and select the criteria for locking the crc-4 multi-frame alignment. the table below shows configurations of the crc-4 selection [1:0] bit of the framing select register (fsr). 12.2.3 how to configure the framer to enable cas multi-frame alignment the xrt84l38 framer can use two algorithms to search for cas multi-frame alignment pattern. upon detecting of cas multi-frame alignment pattern, the framer will declare cas multi-frame alignment synchronization and generate the receive cas multi-frame synchronization pulse (rxcasmsync_n). the framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 0 fas selection bit r/w this read/write bit field allows the user to determine which algorithm is used for searching fas frame alignment pattern. when an fas alignment pattern is found and locked, the xrt84l38 will generate receive synchro - nization (rxsync_n) pulse. 0 - algorithm 1 is selected for searching fas frame alignment pattern. 1 - algorithm 2 is selected for searching fas frame alignment pattern. framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 3-2 crc-4 selection bit r/w theses read/write bit fields allow the user to enable searching of crc-4 multi-frame alignment and determine what criteria are used for locking the crc-4 multi-frame alignment pattern. 00 - searching of crc-4 multi-frame alignment is disabled. the xrt84l38 framer w ill not search for crc-4 multi-frame alignment and thus will not declare crc-4 multi-frame synchronization. no receive crc-4 multi-frame synchronization (rxcrcmsync_n) pulse will be gener - ated by the framer. 01 - searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if: at least one valid crc-4 multi-frame alignment signal is observed within 8 ms. 10 - searching of crc-4 multi-fram e alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if: at least two valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 multi-frame alignment signals is multiple of 2 ms. 11 - searching of crc-4 multi-frame alignment is enabled. the xrt84l38 will search for and declare crc-4 multi-frame synchronization if: at least three valid crc-4 multi-frame alignment signals are observed within 8 ms. the time separating two crc-4 multi-frame alignment signals is multiple of 2 ms.
xrt84l38 374 octal t1/e1/j1 framer rev. 1.0.1 cas selection [1:0] bits of the framing select register (fsr) enable the framer to search for cas multi-frame alignment. the table below shows configurations of the cas selection [1:0] bit of the framing select register (fsr). 12.3 how to configure the framer to apply data and signaling conditioning to received e1 payload data on a per-channel basis the xrt84l38 t1/j1/e1 octal framer provides individual control of each of the thirty two ds0 channels. the user can apply data and signaling conditioning to the received e1 payload data coming from the e1 liu receive block on a per-channel basis. the xrt84l38 framer can apply the following changes to the received e1 payload data coming from the terminal equipment on a per-channel basis: ? all 8 bits of the received payload data are inverted ? the even bits of the received payload data are inverted ? the odd bits of the received payload data are inverted ? the msb of the received payload data is inverted ? all received payload data except the msb are inverted configurations of the xrt84l38 framer to apply the above-mentioned changes to the received e1 payload data are controlled by the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each ds0 channel. the xrt84l38 framer can also replace the incoming e1 payload data from the e1 liu receive block with pre- defined or user-defined codes. the xrt84l38 supports the following conditioning substitutions: ? busy code - an octet with hexadecimal value of 0x7f ? busy_ts code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number ? vacant code - an octet with hexadecimal value of 0xff ? a-law digital milliwatt code framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 5-4 cas selection bit r/w these read/write bit fields allow the user to enable searching of cas multi-frame alignment and determine which algorithm of the two are used for locking the cas multi-frame alignment pattern. 00 - searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer. 01 - searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchronization using algo - rithm 1. 10 - searching of cas multi-frame alignment is enabled. the xrt84l38 will search for and declare cas multi-frame synchronization using algo - rithm 2 (g.732). 11 - searching of cas multi-frame alignment is disabled. the xrt84l38 framer will not search for cas multi-frame alignment and thus will not declare cas multi-frame synchronization. no receive cas multi-frame synchronization (rxcrcmsync_n) pulse will be generated by the framer.
xrt84l38 375 rev. 1.0.1 octal t1/e1/j1 framer ? u-law digital milliwatt code ? idle code - an octet defined by the value stored in the user idle code register (ucr) ? moof code - mux-out-of-frame code with hexadecimal value of 0x1a ? prbs code - an octet generated by the pseudo-random bit sequence (prbs) generator block of the framer once again, configuration of the xrt84l38 framer to replace the received e1 payload data with the above- mentioned coding schemes are controlled by the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each ds0 channel. finally, the xrt84l38 framer can configure any one or ones of the thirty two ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of each channel determine whether that particular channel is configured as d or e channel. the table below illustrates configurations of the receive data conditioning select [3:0] bits of the receive channel control register (rccr). receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it n umber b it n ame b it t ype b it d escription 3-0 receive condition - ing select r/w 0000 - the received e1 payload data of this ds0 channel is unchanged. 0001 - all 8 bits of the input e1 payload data of this ds0 channel are inverted. 0010 - the even bits of the input e1 payload data of this ds0 channel are inverted. 0011 - the odd bits of the input e1 payload data of this ds0 channel are inverted. 0100 - the input e1 payload data of this ds0 channel are replaced by the octet stored in user idle code register (ucr). 0101 - the input e1 payload data of this ds0 channel are replaced by busy code (0x7f). 0110 - the input e1 payload data of this ds0 channel are replaced by vacant code (0xff). 0111 - the input e1 payload data of this ds0 channel are replaced by busy_ts code (111xxxxx). 1000 - the input e1 payload data of this ds0 channel are replaced by mux-out-of-frame (moof) code with value 0x1a. 1001 - the input e1 payload data of this ds0 channel are replaced by the a-law digital milliwatt pattern. 1010 - the input e1 payload data of this ds0 channel are replaced by the u-law digital milliwatt pattern. 1011 - the msb bit of the input e1 payload data of this ds0 channel is inverted. 1100 - all bits of the input e1 payload data of this ds0 channel except msb bit are inverted. 1101 - the input e1 payload data of this ds0 channel are replaced by prbs pattern created by the internal prbs generator of xrt84l38 framer. 1110 - the input e1 payload data of this ds0 channel is unchanged. 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 376 octal t1/e1/j1 framer rev. 1.0.1 when the receive data conditioning select [3:0] bits of the receive channel control register (rccr) of a particular ds0 channel are set to 0100, the received e1 payload data of this ds0 channel are replaced by the octet stored in the receive user idle code register (rucr). the table below shows contents of the receive user idle code register. 12.4 how to configure the xrt84l38 framer to extract robbed-bit signaling information the xrt84l38 t1/j1/e1 octal framer supports insertion of robbed-bit signaling information into the outgoing e1 frame. it also supports extraction and substitution of robbed-bit signaling information from the incoming e1 frame. the following section describes how does the xrt84l38 framer extract and substitute robbed-bit signaling in e1 mode. 12.4.1 configure the framer to receive and extract robbed-bit signaling the xrt84l38 framer supports receiving and extraction of cas signaling. the receive signaling extraction control [1:0] bits of the receive signaling control register (rscr) of each channel select either: ? no signaling extraction ? two-code signaling ? four-code signaling or ? sixteen-code signaling the table below shows configurations of the receive signaling extraction control [1:0] bits of the receive signaling control register. upon receiving and extraction of signaling bits from the incoming e1 frames, the xrt84l38 framer compares the signaling bits with the previously received ones. if there is a change of signaling data, a signaling update (sig) interrupt request may be generated at the end of an e1 multi-frame. the user can thus be notified of a change of signaling data event. to enable the signaling update interrupt, the signaling change interrupt enable bit of the framer interrupt enable register (fier) has to be set. in addition, the t1/e1 framer interrupt enable bit of the block interrupt enable register (bier) needs to be one. receive user idle code register (ucr) (indirect address = 0xn02h, 0x80h - 0x97h) b it n umber b it n ame b it t ype b it d escription 7-0 user idle code r/w these read/write bit-fields permits the user store any value of idle code into the framer. when the receive data conditioning select [3:0] bits of rccr register of a particular ds0 channel are set to 0100, the received e1 payload data are replaced by contents of this register and sent to the terminal equipment. receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xb7h) b it n umber b it n ame b it t ype b it d escription 1-0 signaling extraction control r/w 00 - the xrt84l38 framer does not extract signaling information from incoming e1 payload data. 01 - the xrt84l38 framer extracts sixteen-code signaling information from incoming e1 payload data. 10 - the xrt84l38 framer extracts four-code signaling information from incoming e1 payload data. 11 - the xrt84l38 framer extracts two-code signaling information from incoming e1 payload data.
xrt84l38 377 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the signaling change interrupt enable bit of the framer interrupt enable register. the table below shows configurations of the t1/e1 framer interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the signaling information received is changed, the e1 receive framer block will set the signaling updated status bit of the framer interrupt status register (fisr) to one. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to- clear operation by the microprocessor is required to reset these status indicators. the table below shows the signaling update status bits of the framer interrupt status register. now, there is only one problem remains. since there are thirty two ds0 channels in e1, how do we know signaling information of which channel is changed? to solve this problem, the xrt84l38 provides three 8-bit signaling change registers to indicate the channel(s) which signaling data change had occurred over the last e1 multi-frame period. each bit of the signaling change registers represents one timeslot of the e1 frame. if any particular bit is zero, it means there is no change of signaling data occurred in that particular timeslot over the last e1 multi-frame period. if any particular bit is one, it means there is change of signaling data occurred over the last e1 multi-frame period. framer interrupt enable register (fier) (indirect address = 0xnah, 0x05h) b it n umber b it n ame b it t ype b it d escription 5 signaling change interrupt enable r/w 0 - the signaling update interrupt is disabled. 1 - the signaling update interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 1 t1/e1 framer interrupt enable r/w 0 - every interrupt generated by the framer interrupt status register (fisr) is disabled. 1 - every interrupt generated by the framer interrupt status register (fisr) is enabled. framer interrupt status register (fisr) (indirect address = 0xnah, 0x04h) b it n umber b it n ame b it t ype b it d escription 5 signaling updated rur / wc 0 - there is no change of signaling information in the incoming e1 payload data. 1 - there is change of signaling information in the incoming e1 payload data.
xrt84l38 378 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the signaling change registers. by reading contents of the signaling update status bits of the framer interrupt status register and the signaling change registers, the user can clearly identify which one(s) of the thirty-two ds0 channels has changed signaling information over the last multi-frame period. depending on configurations of the xrt84l38 framer, the signaling bits can be extracted from the incoming e1 frame and direct to all or any one of the following destinations: ? signaling data is stored to receive signaling register array (rsra) of each channel ? signaling data is sent to the terminal equipment through the receive signaling output pin (rxsig_n) ? signaling data is sent to the terminal equipment through the receive overhead output pin (rxoh_n) ? signaling data is embedded into the output pcm data sending towards the terminal equipment through the receive serial output pin (rxser_n) the follow sections discuss how to configure the xrt84l38 framer to extract signaling information bits and send them to different destinations. 12.4.1.1 store signaling bits into rsra register array the four least significant bits of the receive signaling register array (rsra) of each timeslot can be used to store received signaling data. the user can read these bits through microprocessor access. if the xrt84l38 framer is configure to extract signaling bits from incoming e1 payload data, the e1 receive framer block will strip off the cas signaling bits from time slot 16 of the incoming e1 frames and store them into appropriate locations of the rsra. the extraction of signaling bit from e1 pcm data is done on a per-channel basis. the bit 3 of rsra register is used to hole signaling bit a. bit 2 is used to hold signaling bit b. bit 1 is used to hold signaling bit c. bit 0 is used to hold signaling bit d. the table below shows the four least significant bits of the receive signaling register array. 12.4.1.2 outputting signaling bits through rxsig_n pin the xrt84l38 framer can be configure to output extracted signaling bits to external equipment through the rxsig_n pins. this pin is a multiplexed i/o pin with two functions: ? rxtsb[0]_n - receive timeslot number bit [0] output pin signaling change registers (scr) (indirect address = 0xn0h, 0x0dh - 0x10h) l ocation \ b it b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 0xn0h - 0x0dh ch 0 ch 1 ch 2 ch 3 ch 4 ch 5 ch 6 ch 7 0xn0h - 0x0eh ch 8 ch 9 ch 10 ch 11 ch 12 ch 13 ch 14 ch 15 0xn0h - 0x0fh ch 16 ch 17 ch 18 ch 19 ch 20 ch 21 ch 22 ch 23 0xn0h - 0x0fh ch 24 ch 25 ch 26 ch 27 ch 28 ch 29 ch 30 ch 31 receive signaling register array (rsra) (indirect address = 0xn4h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 3 signaling bit a r/w this bit is used to store signaling bit a that is received and extracted. 2 signaling bit b r/w this bit is used to store signaling bit b that is received and extracted. 1 signaling bit c r/w this bit is used to store signaling bit c that is received and extracted. 0 signaling bit d r/w this bit is used to store signaling bit d that is received and extracted.
xrt84l38 379 rev. 1.0.1 octal t1/e1/j1 framer ? rxsig_n - receive signaling output pin when the receive fractional e1 bit of the receive interface control register (ricr) is set to 0, this pin is configured as rxtsb[0]_n pin, it outputs bit 0 of the timeslot number of the e1 pcm data that is receiving. when the receive fractional e1 bit of the receive interface control register (ricr) is set to 1, this pin is configured as rxsig_n pin, it acts as an output source for the signaling bits to be received in the inbound e1 frames. the table below shows configurations of the receive fractional e1 bit of the receive interface control register (ricr). figure 125 below is a timing diagram of the rxsig_n output pin. please note that the signaling bit a of a certain timeslot coincides with bit 3 of the received serial output data; signaling bit b coincides with bit 2 of the received serial output data; signaling bit c coincides with bit 1 of the received serial output data and signaling bit d coincides with bit 0 of the received serial output data. 12.4.1.3 outputting signaling bits from rxoh_n pin the xrt84l38 framer can be configure to output extracted signaling bits to external equipment through the receive overhead rxoh_n output pins. the rxoh_n pin can acts as an output source for the signaling bits to be received in the inbound e1 frames. when this pin is chosen as the output source for the signaling bits, any data presents in time slot 16 of the incoming e1 frames would be presented onto the pin directly. please note that the signaling bit a of channel 1-15 coincides with bit 1 of the pcm data; signaling bit b channel 1-15 coincides with bit 2 of the pcm data; signaling bit c channel 1-15 coincides with bit 3 of the pcm; signaling bit d channel 1-15 coincides with bit 4 of the pcm data. similarly, the signaling bit a of channel 17-31 coincides with bit 5 of the pcm data; signaling bit b channel 17-31 coincides with bit 6 of the pcm data; signaling bit c channel 17-31 coincides with bit 7 of the pcm; signaling bit d channel 17-31 coincides with bit 8 of the pcm data. figure 126 below is a timing diagram of the rxoh_n output pin. receive interface control register (r icr) (indirect address = 0xn0h, 0x20h) b it n umber b it n ame b it t ype b it d escription 4 receive fractional e1 r/w this read/write bit-field permits the user to determine which one of the two functions the multiplexed i/o pin of rxtsb[0]_n/rxsig_n is spotting. 0 - this pin is configured as rxtsb[0]_n pin, it outputs bit 0 of the timeslot number of the e1 pcm data that is receiving. 1 - this pin is configured as rxsig_n pin, it acts as an output source for the signaling bits to be received in the inbound e1 frames f igure 125. t iming diagram of r x s ig _ n o utput pin f igure 126. t iming diagram of the r x oh_ n o utput pin rxserclk rxser rxsig input data input data timeslot 16 timeslot 0 timeslot 5 timeslot 6 c a b d c a b d c a b d c a b d
xrt84l38 380 octal t1/e1/j1 framer rev. 1.0.1 (redraw) figure ?: timing diagram of the rxoh_n output pin the receive signaling output enable bit of the receive signaling control register (rscr) determines whether the extracted signaling bits will be sent through the receive overhead output pin (rxoh_n) to external equipments. the table below shows configurations of the receive overhead output enable bit of the receive signaling control register. 12.4.1.4 send signaling data through rxser_n pin as mentioned in the above sections, signaling information embedded in the incoming e1 pcm data can be sent to either the rsra register array and/or sent through the receive signaling output pin, at the same time, the signaling data will be directed to the receive serial data output pin together with other incoming e1 payload data. the external equipment can thus still extract signaling data from the received e1 payload data separately. 12.4.1.5 signaling data substitution after channel conditioning, the signaling conditioning can be optionally enabled by the rscr registers. the actual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the receive substitution signaling register (rssr). to enable signaling substitution, the receive signaling substitution enable bit of the receive signaling control register (rscr) has to be set to one. the table below shows configuration of the receive signaling substitution enable bit of the receive signaling control register. as mentioned before, the actual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the receive substitution signaling register (rssr). the table below shows configurations of the receive substitution signaling register. receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xbfh) b it n umber b it n ame b it t ype b it d escription 5 receive signaling output enable r/w 0 - the xrt84l38 framer w ill not s end extracted signaling bits from the incoming e1 payload data to external equipment through the receive overhead output pin (rxoh_n). 1 - the xrt84l38 framer will send extracted signaling bits from the incom - ing e1 payload data to external equipment through the receive overhead output pin (rxoh_n). receive signaling control register (rscr) (indirect address = 0xn2h, 0xa0h - 0xbfh) b it n umber b it n ame b it t ype b it d escription 6 receive signaling substitution enable r/w 0 - signaling substitution is disabled. the xrt84l38 framer will not replace extracted signaling bits from the incoming e1 payload data with all ones or with signaling bits stored in rssr registers. 1 - signaling substitution is enabled. the xrt84l38 framer will replace extracted signaling bits from the incoming e1 payload data with all ones or with signaling bits stored in rssr registers. receive substitution signaling register (rssr) (indirect address = 0xn02h, 0x80h - 0x9fh) b it n umber b it n ame b it t ype b it d escription 7-4 reserved r/w 3 sig16-a sig4-a sig2-a sixteen-code signaling bit a four-code signaling bit a two-code signaling bit a
xrt84l38 381 rev. 1.0.1 octal t1/e1/j1 framer the receive signaling substitution control [1:0] bits can select all ones substitution, two-code signaling substitution, four-code signaling substitution, or sixteen-code signaling. the xrt84l38 framer can substitute received signaling bits with all ones. two-code signaling substitution is done by substituting all the four signaling bits with the content of the sig2-a bit of the register. four-code signaling substitution is done by substituting the first two signaling bits of the four with the sig4-a bit and the last two signaling bits of the four with the sig4-b bit of the rssr register. sixteen-code signaling substitution is implemented by substituting the four signaling bits with the content of sig16-a, sig16-b, sig16-c, and sig16-d bits of rssr register respectively. the table below shows configurations of the receive signaling substitution control [1:0] bits of the receive signaling control register. 12.5 how to configure the framer to detect alarms and error conditions the xrt84l38 t1/j1/e1 octal framer can be configured to monitor quality of received e1 frames. it can generate error indicators if the local receive framer has received error frames from the remote terminal. if corresponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. upon microprocessor interruption, the user can intervene by looking into the error conditions. at the same time, the user can configure the xrt84l38 framer to receive alarms and error indications to remote terminal. different alarms and error indications will be received depending on the error condition. the section below gives a brief discussion of the error conditions that can be detected by the xrt84l38 framer and error indications that will be generated. 12.5.1 how to configure the framer to detect ais alarm 2 sig16-b sig4-b sig2-a sixteen-code signaling bit b four-code signaling bit b two-code signaling bit a 1 sig16-c sig4-a sig2-a sixteen-code signaling bit c four-code signaling bit a two-code signaling bit a 0 sig16-d sig4-b sig2-a sixteen-code signaling bit d four-code signaling bit b two-code signaling bit a receive signaling control register (rscr) (indirect address = 0xn2h, 0x40h - 0x5fh) b it n umber b it n ame b it t ype b it d escription 3-2 receive signaling substitution con - trol r/w 00 - the received signaling bits are replaced by all ones and send to the external equipment. 01 - two-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. 10 - four-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. 11 - sixteen-code signaling substitution is applied to the received signaling bits. the replaced signaling information is sent to the external equipment. receive substitution signaling register (rssr) (indirect address = 0xn02h, 0x80h - 0x9fh) b it n umber b it n ame b it t ype b it d escription
xrt84l38 382 octal t1/e1/j1 framer rev. 1.0.1 transmission of alarm indication signal (ais) or blue alarm by the intermediate node indicates that the equipment is still functioning but unable to offer services. it is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. the xrt84l38 framer can detect three types of ais in e1 mode: ? framed ais ? unframed ais ? ais16 unframed ais is an all ones pattern. if unframed ais is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received ais signal. however, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare loss of frame (lof). on the other hand, the payload portion of a framed ais pattern is all ones. however, a framed ais pattern still has correct framing bits. therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. in this case, no lof or red alarm will be declared. "ais16" is an ais alarm that only supported in e1 framing format. it is an all ones pattern in time slot 16 of each e1 frame. as we mentioned before, time slot 16 is usually used for signaling and data link in e1, therefore, an "ais16" alarm is transmitted by the intermediate node to indicate that the data link channel is having a problem. since all the other thirty one time slots are still transmitting normal data (that is, framing information and pcm data), therefore, the equipment further down the line can still maintain frame synchronization, timing synchronization as well as receiving pcm data. in this case, no lof or red alarm will be declared by the equipments further down the line. however, a cas multi-frame yellow alarm will be sent by the equipment further down the line to indicate the loss of cas multi-frame alignment. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for ais (both framed and unframed) and ais16 errors. ais alarm condition are detected and declared according to the following procedure: 1. the incoming e1 frames are monitored for ais detection. ais detection is defined as an unframed or framed pattern with less than three zeros in two consecutive frames. in the case of framed ais, time slot 0 is excluded. 2. an ais detection counter within the receive framer block of the xrt84l38 counts the occurrences of ais detection over a 4 ms interval. it will indicate a valid ais flag when thirteen or more of a possible sixteen ais are detected. 3. each 4 ms interval with a valid ais flag increments a flag counter which declares ais alarm when 25 valid flags have been collected. therefore, ais condition has to be persisted for 104 ms before ais alarm condition is declared by the xrt84l38 framer. if there is no valid ais flag over a 4ms interval, the alarm indication logic will decrement the flag counter. the ais alarm is removed when the counter reaches 0. that is, ais alarm will be removed if in over 104 ms, there is no valid ais flag. ais16 alarm condition are detected and declared according to the following procedure: 1. the incoming e1 frames are monitored for ais16 detection. ais16 detection is defined as two consecutive all ones time slot 16 bytes while cas multi-frame alignment pattern is missing or cas multi-frame is out of synchronization. 2. an ais16 detection counter within the receive framer block of the xrt84l38 counts the occurrences of ais16 detection. 3. each valid ais flag increments a flag counter which declares ais alarm when 22 valid flags have been col - lected.
xrt84l38 383 rev. 1.0.1 octal t1/e1/j1 framer if there is no valid ais16 flag, the alarm indication logic will decrement the flag counter. the ais16 alarm is removed when the counter reaches 0. the alarm indication signal detection select [1:0] bits of the alarm generation register (agr) enable the three types of ais detection that are supported by the xrt84l38 framer. the table below shows configurations of the alarm indication signal detection select [1:0] bits of the alarm generation register (agr). if detection of unframed or framed ais alarm is enabled by the user and if ais is present in the incoming e1 frame, the xrt84l38 framer can generate a receive ais state change interrupt associated with the setting of receive ais state change bit of the alarm and error status register to one. to enable the receive ais state change interrupt, the receive ais state change interrupt enable bit of the alarm and error interrupt enable register (aeier) have to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive ais state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and ais is present in the incoming e1 frame, the xrt84l38 framer will declare ais by doing the following: ? set the read-only receive ais state bit of the alarm and error status register (aesr) to one indicating there is ais alarm detected in the incoming e1 frame. ? set the receive ais state change bit of the alarm and error status register to one indicating there is a change in state of ais. this status indicator is valid until the framer interrupt status register is read. alarm generation register (agr) (indirect address = 0xn0h, 0x08h) b it n umber b it n ame b it t ype b it d escription 1-0 ais detection select r/w 00 - ais alarm detection is disabled. 01 - detection of unframed ais alarm of all ones pattern is enabled. 10 - detection of ais16 alarm is enabled. 11 - detection of framed ais alarm of all ones pattern except for framing bits is enabled. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 1 receive ais state change interrupt enable r/w 0 - the receive ais state change interrupt is disabled. 1 - the receive ais state change interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled.
xrt84l38 384 octal t1/e1/j1 framer rev. 1.0.1 reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive ais state change status bits of the alarm and error status register. the receive ais state bit of the alarm and error status register (aesr), on the other hand, is a read-only bit indicating there is ais alarm detected in the incoming e1 frame. the table below shows the receive ais state status bits of the alarm and error status register. 12.5.2 how to configure the framer to detect red alarm the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for red alarm or loss of frame (lof) condition. red alarm condition are detected and declared according to the following procedure: 1. the red alarm is detected by monitoring the occurrence of loss of frame (lof) over a 4 ms interval. 2. an lof valid flag will be posted on the interval when one or more lof occurred during the interval. 3. each interval with a valid lof flag increments a flag counter which declares red alarm when 25 valid intervals have been accumulated. 4. an interval without valid lof flag decrements the flag counter. the red alarm is removed when the counter reaches zero. if lof condition is present in the incoming e1 frame, the xrt84l38 framer can generate a receive red alarm state change interrupt associated with the setting of receive red alarm state change bit of the alarm and error status register to one. to enable the receive red alarm state change interrupt, the receive red alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 1 receive ais state change rur / wc 0 - there is no change of ais state in the incoming e1 payload data. 1 - there is change of ais state in the incoming e1 payload data. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 6 receive ais state r 0 - there is no ais alarm condition detected in the incoming e1 payload data. 1 - there is ais alarm condition detected in the incoming e1 payload data.
xrt84l38 385 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the receive red alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and red alarm is present in the incoming e1 frame, the xrt84l38 framer will declare red alarm by doing the following: ? set the read-only receive red alarm state bit of the alarm and error status register (aesr) to one indicating there is red alarm detected in the incoming e1 frame. ? set the receive red alarm state change bit of the alarm and error status register to one indicating there is a change in state of red alarm. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive red alarm state change status bits of the alarm and error status register. the receive red alarm state bit of the alarm and error status register (aesr), on the other hand, is a read- only bit indicating there is red alarm detected in the incoming e1 frame. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 2 receive red alarm state change interrupt enable r/w 0 - the receive red alarm state change interrupt is disabled. no receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. 1 - the receive red alarm state change interrupt is enabled. receive loss of frame (rxlof) interrupt will be generated upon detection of lof condition. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 2 receive red alarm state change rur / wc 0 - there is no change of red alarm state in the incoming e1 payload data. 1 - there is change of red alarm state in the incoming e1 payload data.
xrt84l38 386 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the receive red alarm state status bits of the alarm and error status register. 12.5.3 how to configure the framer to detect yellow alarm the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for yellow alarm condition. the yellow alarm is detected and declared according to the following procedure: 1. monitor the occurrence of yellow alarm pattern over a 4 ms interval. a yel valid flag will be posted on the interval when yellow alarm pattern occurred during the interval. 2. each interval with a valid yel flag increments a flag counter which declares yel alarm when 80 valid intervals have been accumulated. 3. an interval without valid yel flag decrements the flag counter. the yel alarm is removed when the counter reaches zero. if yellow alarm condition is present in the incoming e1 frame, the xrt84l38 framer can generate a receive yellow alarm state change interrupt associated with the setting of receive yellow alarm state change bit of the alarm and error status register to one. to enable the receive yellow alarm state change interrupt, the receive yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and yellow alarm is present in the incoming e1 frame, the xrt84l38 framer will declare yellow alarm by doing the following: alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 7 receive red alarm state r 0 - there is no red alarm condition detected in the incoming e1 payload data. 1 - there is red alarm condition detected in the incoming e1 payload data. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 0 receive yellow alarm state change interrupt enable r/w 0 - the receive yellow alarm state change interrupt is disabled. any state change of receive yellow alarm will not generate an interrupt. 1 - the receive yellow alarm state change interrupt is enabled. any state change of receive yellow alarm will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled.
xrt84l38 387 rev. 1.0.1 octal t1/e1/j1 framer ? set the receive yellow alarm state change bit of the alarm and error status register to one indicating there is a change in state of yellow alarm. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive yellow alarm state change status bits of the alarm and error status register. 12.5.4 how to configure the framer to detect cas multi-frame yellow alarm the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for cas multi-frame yellow alarm condition. the cas multi-frame yellow alarm is detected and declared according to the following procedure: 1. monitor the occurrence of cas multi-frame yellow alarm pattern over a 4 ms interval. an myel valid flag will be posted on the interval when cas multi-frame yellow alarm pattern occurred during the interval. 2. each interval with a valid myel flag increments a flag counter which declares myel alarm when 80 valid intervals have been accumulated. 3. an interval without valid myel flag decrements the flag counter. the myel alarm is removed when the counter reaches zero. if cas multi-frame yellow alarm condition is present in the incoming e1 frame, the xrt84l38 framer can generate a receive cas multi-frame yellow alarm state change interrupt associated with the setting of receive cas multi-frame yellow alarm state change bit of the alarm and error status register to one. to enable the receive cas multi-frame yellow alarm state change interrupt, the receive cas multi-frame yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive cas multi-frame yellow alarm state change interrupt enable bit of the alarm and error interrupt enable register (aeier). alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 0 receive yellow alarm state change rur / wc 0 - there is no change of yellow alarm state in the incoming e1 payload data. 1 - there is change of yellow alarm state in the incoming e1 payload data. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 5 receive cas multi-frame yellow alarm state change interrupt enable r/w 0 - the receive cas multi-frame yellow alarm state change interrupt is disabled. any state change of receive cas multi-frame yellow alarm w ill not generate an interrupt. 1 - the receive cas multi-frame yellow alarm state change interrupt is enabled. any state change of receive cas multi-frame yellow alarm will generate an interrupt.
xrt84l38 388 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and cas multi-frame yellow alarm is present in the incoming e1 frame, the xrt84l38 framer will declare cas multi-frame yellow alarm by doing the following: ? set the receive cas multi-frame yellow alarm state change bit of the alarm and error status register to one indicating there is a change in state of cas multi-frame yellow alarm. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive cas multi-frame yellow alarm state change status bits of the alarm and error status register. 12.5.5 how to configure the framer to detect bipolar violation the line coding for the e1 signal should be bipolar. that is, a binary "0" is received as zero volts while a binary "1" is received as either a positive or negative pulse, opposite in polarity to the previous pulse. a bipolar violation or bpv occurs when the alternate polarity rule is violated. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for bipolar violations. if a bipolar violation is present in the incoming e1 frame, the xrt84l38 framer can generate a receive bipolar violation interrupt associated with the setting of receive bipolar violation bit of the alarm and error status register to one. to enable the receive bipolar violation interrupt, the receive bipolar violation interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 5 receive cas multi-frame yellow alarm state change rur / wc 0 - there is no change of cas multi-frame yellow alarm state in the incom - ing e1 payload data. 1 - there is change of cas multi-frame yellow alarm state in the incoming e1 payload data.
xrt84l38 389 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the receive bipolar violation interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and one or more bipolar violations are present in the incoming e1 frame, the xrt84l38 framer will declare receive bipolar violation by doing the following: ? set the receive bipolar violation bit of the alarm and error status register to one indicating there are one or more bipolar violations. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive bipolar violation status bits of the alarm and error status register. 12.5.6 how to configure the framer to detect loss of signal a loss of signal or los occurs when neither rpos nor rneg inputs of the framer receives a high level input for 32 consecutive bit times. the alarm indication logic within the receive framer block of the xrt84l38 framer monitors the incoming e1 frames for loss of signal conditions. if used in conjunction with exar lius, for example, the xrt83l3x family, the xrt84l38 framer also declares los when the receive los (rxlos) input pin is pulled high. the removal of los condition is through detection of 12.5% ones over 32 consecutive bits. in the other words, xrt84l38 framer will remove los alarm when there is no 4 consecutive zeros received. n ote : the implementation of los detection and removal only apply to b8zs coded bipolar inputs. alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 3 receive bipolar violation interrupt enable r/w 0 - the receive bipolar violation interrupt is disabled. occurrence of one or more bipolar violations will not generate an interrupt. 1 - the receive bipolar violation interrupt is enabled. occurrence of one or more bipolar violations will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 3 receive bipolar violation state change rur / wc 0 - there is no change of bipolar violation state in the incoming e1 pay - load data. 1 - there is change of bipolar violation state in the incoming e1 payload data.
xrt84l38 390 octal t1/e1/j1 framer rev. 1.0.1 if loss of signal condition is present in the incoming e1 frame, the xrt84l38 framer can generate a receive loss of signal interrupt associated with the setting of receive loss of signal bit of the alarm and error status register to one. to enable the receive loss of signal interrupt, the receive loss of signal interrupt enable bit of the alarm and error interrupt enable register (aeier) has to be set to one. in addition, the alarm and error interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive loss of signal interrupt enable bit of the alarm and error interrupt enable register (aeier). the table below shows configurations of the alarm and error interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and one or more loss of signals are present in the incoming e1 frame, the xrt84l38 framer will declare receive loss of signal by doing the following: ? set the receive loss of signal bit of the alarm and error status register to one indicating there is one or more loss of signals. this status indicator is valid until the framer interrupt status register is read. reading this register clears the associated interrupt if reset-upon-read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive loss of signal status bits of the alarm and error status register. 13.0 ds1 hdlc controller block 13.1 ds1 transmit hdlc controller block 13.1.1 description of the ds1 transmit hdlc controller block alarm and error interrupt enable register (aeier) (indirect address = 0xnah, 0x03h) b it n umber b it n ame b it t ype b it d escription 4 receive loss of signal interrupt enable r/w 0 - the receive loss of signal interrupt is disabled. occurrence of loss of signals will not generate an interrupt. 1 - the receive loss of signal interrupt is enabled. occurrence of loss of signals will generate an interrupt. block interrupt enable register (bier) (indirect address = 0xnah, 0x01h) b it n umber b it n ame b it t ype b it d escription 1 alarm and error interrupt enable r/w 0 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is disabled. 1 - every interrupt generated by the alarm and error interrupt status reg - ister (aeisr) is enabled. alarm and error status register (aesr) (indirect address = 0xnah, 0x02h) b it n umber b it n ame b it t ype b it d escription 4 receive loss of signal state rur / wc 0 - there is no change of loss of signal state in the incoming e1 payload data. 1 - there is change of loss of signal state in the incoming e1 payload data.
xrt84l38 391 rev. 1.0.1 octal t1/e1/j1 framer xrt84l38 allows user to insert data link information to outbound ds1 frames. the data link information in ds1raming format mode can be inserted from: ? ds1 transmit overhead input interface block ? ds1 transmit hdlc controller ? ds1 transmit serial input interface the transmit data link source select [1:0] bits, within the transmit data link select register (tsdlsr) determine source of the data link bits (facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in slc?96 framing format mode and remote signaling (r) bits in t1dm framing format mode) to be inserted into the outgoing ds1 frames. the table below shows configuration of the transmit data link source select [1:0] bits of the transmit data link select register (tsdlsr). if the transmit data link source select bits of the transmit data link select register are set to 00, the transmit hdlc controller block becomes input source of the data link bits in outgoing ds1 frames. each of the eight framers within the xrt84l38 device contains a ds1 transmit high-level data link controller (hdlc) block. the function of this block is to provide a serial data link channel in ds1 mode through the following: ? facility data link (fdl) bits in esf framing format mode ? signaling framing (fs) bits in slc?96 framing format mode ? remote signaling (r) bits in t1dm framing format mode ? d or e signaling timeslot channel data link bits are automatically inserted into the facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in slc?96 framing format mode and remote signaling (r) bits in t1dm framing format mode or forced to 1 by the framer. additionally, xrt84l38 allows the user to define any one of ones of the twenty-four ds0 timeslots to be d or e channel. we will discuss how to configure xrt84l38 to transmit data link information through d or e channels in later section. the ds1 transmit hdlc controller block contains three major functional modules associated with ds1 framing formats. they are the: ? slc?96 data link controller ? lapd controller ? bit-oriented signaling processor. there are two 96-byte transmit message buffers in shared memory for each of the eight framers to transmit data link information. when one message buffer is filled up, the transmit hdlc controller automatically switches to the next message buffer to load data link messages. these two message buffers ping-pong among each other for data link message transmission. transmit data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 1-0 transmit data link source select [1:0] r/w 00 - the data link bits are inserted into the framer through the transmit hdlc controller. 01 - the data link bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 10 - the data link bits are inserted into the framer through the transmit over - head input interface via the txoh_n pins. 11 - the data link bits are forced into 1.
xrt84l38 392 octal t1/e1/j1 framer rev. 1.0.1 the slc?96 enable bit and the lapd enable bit of the data link control register (dlcr) determines which one of the three functions is performed by the transmit hdlc controller block. the table below shows configuration of the slc?96 enable bit of the data link control register (dlcr). the table below shows configuration of the lapd enable bit of the data link control register (dlcr). 13.1.2 how to configure xrt84l38 to transmit data link information through d or e channels the xrt84l38 can configure any one or ones of the twenty-four ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the transmit data conditioning select [3:0] bits of the transmit channel control register (tccr) of each channel determine whether that particular channel is configured as d or e channel. these bits also determine what type of data or signaling conditioning is applied to each channel. if the transmit data conditioning select [3:0] bits of the transmit channel control register of a particular timeslot are set to 1111, that timeslot is configured as a d or e timeslot. any d or e timeslot can be configured to take data link information from the following sources: ? ds1 transmit overhead output interface block ? ds1 transmit hdlc controller block ? ds1 transmit serial output interface block ? ds1 transmit fractional input interface block the transmit d or e channel source select [1:0] bits of the transmit data link select register (tsdlsr) determines which one of the above-mentioned modules to be input sources of d or e timeslot. the table below data link control register (dlcr) indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 7 slc?96 enable r/w 0 - in slc?96 framing mode, the data link transmission is disabled. the framer transmits the regular sf framing bits. in esf framing mode, the framer transmits regular esf framing bits and facility data link (fdl) bits. 1 - in slc?96 framing mode, the data link transmission is enabled. in esf framing mode, the framer transmits slc?96-like message in the facility data link bits. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 0 lapd enable r/w 0 - the transmit hdlc controller will send out bit-oriented signaling (bos) message. 1 - the transmit hdlc controller will send out lapd protocol or so-called mes - sage-oriented signaling (mos) message. transmit channel control register (tccr) (indirect address = 0xn2h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 3-0 transmit data conditioning select r/w 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 393 rev. 1.0.1 octal t1/e1/j1 framer shows configuration of the transmit d or e channel source select [1:0] bits of the transmit data link select register (tsdlsr). for the transmit hdlc controller to be input source of d or e channel, the transmit d or e channel source select [1:0] bits of the transmit data link select register has to be set to 01. 13.1.3 transmit bos (bit oriented signaling) processor the transmit bos processor handles transmission of bos messages through the ds1 data link channel. it determines how many repetitions a certain bos message will be transmitted. it also inserts bos idle flag sequence and abort sequence to be transmitted on the data link channel. in the later sections, we will discuss bos message format and how to transmit bos message. 13.1.3.1 description of bos bit-oriented signaling message is a sixteen-bit pattern carries the form of: (0d5d4d3d2d1d00 11111111) where d5 is the msb and d0 is the lsb. the rightmost "1" is transmitted first. bit-oriented signaling message is classified into the following two groups: ? priority codeword message ? command and response information priority codeword message is preemptive and has the highest priority among all data link information. priority codeword information indicates a condition that is affecting the quality of service and thus shall be transmitted until the condition no longer exists. the duration of transmission should not be less than one second. priority codeword information may be interrupted by software for 100 milliseconds to send maintenance commands with a minimum interval of one second between interruptions. yellow alarm (00000000 11111111) is the only priority message defined in standard. command and response information is transmitted to perform various functions. the bos processor send command and response message by transmitting a minimum of 10 repetitions of the appropriate codeword pattern. command and response data transmission initiates action at the remote end, while the remote end will respond by sending bit-oriented response message to acknowledge the received commands. the activation and deactivation of line loop-back and payload loop-back functions are this type of signal. 13.1.3.2 how to configure the bos processor block to transmit bos this section describes how to configure the bos processor block to transmit bos message in a step-by-step basis. 13.1.3.2.1 step 1: find out the next available transmit data link buffer to transmit a bit-oriented signal, a repeating message is sent of the form (0d5d4d3d2d1d00 11111111), where the "d5d4d3d2d1d0" represents a six-bit message. the user is recommended to read transmit data link byte count register for next available transmit data link buffer number. transmit data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 3-2 transmit d or e channel source select [1:0] r/w 00 - the data link bits are inserted into the d or e channel through the transmit serial data input interface via the txser_n pins. 01 - the data link bits are inserted into the d or e channel through the transmit hdlc controller. 10 - the data link bits are inserted into the d or e channel through the transmit serial data input interface via the txser_n pins. 11 - the data link bits are inserted into the d or e channel through the transmit fractional t1 input interface via the txfrt1_n pins.
xrt84l38 394 octal t1/e1/j1 framer rev. 1.0.1 the table below shows how content of the buffer enable bit of the transmit data link byte count register (tdlbcr) determines what the next available transmit data link buffer number is. 13.1.3.2.2 step 2: write bos message into transmit data link buffer after finding out the next available transmit data link buffer, the user should write the eight bits message that are to be transmitted in the form (0d5d4d3d2d1d00) to the first location of the next available transmit data link buffer. the writing of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for transmit data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the transmit data link buffer and a microcontroller read will access the receive data link buffers. the very first write access to the lapd buffer indirect data register will always be direct to location 0 within the transmit data link buffer. for example, if the bos message to be sent is (101011) and the next available transmit data link buffer of channel n is 1. the user should write pattern (01010110) into transmit data link buffer 1 of channel n. the following microprocessor access to the framer should be done: wr n7h 56h 13.1.3.2.3 step 3: program bos message transmission repetitions the user should program the value of message transmission repetitions into the transmit data link byte count register. the framer will transmit the bos message the same number of times as was stored in the transmit data link byte count register (tdlbcr) before generating the transmit end of transfer (txeot) interrupts. if the value stored inside the transmit data link byte count register (tdlbcr) is set to 0, the message will be transmitted indefinitely and no transmit end of transfer interrupt will be generated. the table below shows configurations of the transmit data link byte count [6:0] bits the transmit data link byte count register (tdlbcr). 13.1.3.2.4 step 4: configure bos message transmission control bits configuration of the data link control register determines whether the bos processor will insert idle flag character or abort sequence to the data link channel. it also determines how the transition between mos mode to bos mode is done. if the idle insertion bit of the data link control register is set, repeated flags of value 0x7e are transmitted as soon as the current operation is finished (defined by the value in transmit data link byte count register). transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it n umber b it n ame b it t ype b it d escription 7 buffer select r 0 - the next available transmit data link buffer for sending out bos or mos message is buffer 0. 1 - the next available transmit data link buffer for sending out bos or mos message is buffer 1. transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it n umber b it n ame b it t ype b it d escription 6-0 transmit data link byte count [6:0] r/w value of these bits determines how many times a bos message pattern will be transmitted by the framer before generating the transmit end of transfer (txeot) interrupt. n ote : if these bits are set to 0, the bos message will be transmitted indefinitely and no transmit end of transfer interrupts will be generated.
xrt84l38 395 rev. 1.0.1 octal t1/e1/j1 framer however, if the transmit data link byte count value is zero, the framer will not force a flag sequence on to the data link channel. the table below shows configurations of the idle insertion bit of the data link control register (dlcr). if the abort bit of the data link control register is set, a bos abort sequence (9 consecutive ones) is transmitted on the data link channel following by all-one transmission. in other words, all data link bits will be set to 1 after the transmission of the current message byte. the table below shows configurations of the abort bit of the data link control register (dlcr). switching the data link channel from mos mode to bos mode while a message is being transmitted will interrupt the message after the octet in progress is transmitted. if the mos abort bit of the data link control register is set, a mos abort sequence (a zero followed by 7 ones) will be inserted before switching. switching the data link from bos to lapd will not take place until the current operation completes if transmit bos byte count is not set to zero initially. if the transmit bos byte count value is set to zero, the transition from bos mode to mos mode will take place right after finishing the current message octet. the table below shows configurations of the mos abort bit of the data link control register (dlcr). 13.1.3.2.5 step 5: enable transmit bos message interrupts the bos processor can generate a couple of interrupts indicating the status of bos message transmission to the microprocessor. these are the transmit start of transfer (txsot) interrupt and the transmit end of transfer (txeot) interrupt. to enable these interrupts, the transmit start of transfer enable bit and the transmit end of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 2 idle insertion r/w 0 - no flag sequence is sent on the data link channel. 1 - the framer forces a flag sequence of value 0x7e onto the data link channel. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 3 abort r/w 0 - no abort sequence is sent on the data link channel. 1 - the framer forces an abort sequence of pattern ( 111111111) onto the data link channel. all data link bits will be set to 1 after sending the abort sequence. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 6 mos abort r/w 0 - the framer forces an mos abort sequence of one zero and seven ones (0 1111111) onto the data link ch annel during the transition from mos mode to bos mode. 1 - no mos abort sequence is sent on the data link channel during the transition from mos mode to bos mode.
xrt84l38 396 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the transmit start of transfer enable bit and the transmit end of transfer enable bit of the data link interrupt enable register. the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the bos message is transmitted to the data link channel, the bos processor changes the transmit start of transfer and transmit end of transfer status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the transmit start of transfer and transmit end of transfer status bits of the data link status register. 13.1.3.2.6 step 6: bos message transmission a zero is then written into the lapd enable bit of data link control register, which sets the transmitter to bit- oriented mode and kicks off the transmission process. the lapd controller latches these control bits of the data link control register and send a transmit start of transfer interrupt (txsot) to the microprocessor to indicate that a bos message will be send. after the required number of times of bos message is sent, the lapd controller generates an transmit end of transfer interrupt (txeot) to the microprocessor to indicate that the bos message transmission comes to an end. data link interrupt enable register (dlier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer enable r/w 0 - the transmit start of transfer interrupt is disabled. 1 - the transmit start of transfer interrupt is enabled. 4 transmit end of transfer enable r/w 0 - the transmit end of transfer interrupt is disabled. 1 - the transmit end of transfer interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer rur / wc 0 - there is no data link message to be sent to the data link channel. 1 - the hdlc controller will send a data link message to the data link channel. 4 transmit end of transfer rur / wc 0 - no data link message was sent to the data link channel. 1 - the hdlc controller finished sending a data link message to the data link channel.
xrt84l38 397 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the lapd enable bit of the data link control register (dlcr). 13.1.4 transmit mos (message oriented signaling) or lapd controller the transmit lapd controller implements the message-oriented protocol based on itu recommendation q.921 link access procedures on the d-channel (lapd) type of protocol. it provides the following functions: ? zero stuffing ? t1/e1 transmitter interface ? transmit message buffer access ? frame check sequence generation ? idle flag insertion ? abort sequence generation two 96-byte buffers in shared memory are allocated for lapd transmitter to reduce the frequency of microprocessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt. there are no restrictions on the length of the message. however the 96-byte buffer is deep enough to hold one entire lapd path or test signal identification message. figure 127 depicts the block diagram of both transmit and receive lapd controller. in the later sections, we will briefly discuss mos message format and how to configure the lapd controller to transmit mos message. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 0 lapd enable r/w 0 - the transmit hdlc controller will send out bit-oriented signaling (bos) message. 1 - the transmit hdlc controller will send out lapd protocol or so-called message-oriented signaling (mos) message. f igure 127. lapd c ontroller memory rx state machine zero deletion fcs generator multi-port memory interface up pio & dma interface memory request & address generation tx register rx register fcs check zero stuffing tx state machine (rx) req, ack, addr (tx) req, ack, rdy, addr rxlapddata rxlapdack rxlapdrdy txlapdrdy txlapdack txlapddata fcs crc error mtxclk
xrt84l38 398 octal t1/e1/j1 framer rev. 1.0.1 13.1.4.1 discussion of mos message-oriented signals (mos) sent by the transmit lapd controller are messages conforming to itu recommendation q.921 lapd protocol as defined below. two types of message-oriented signals are defined. one is a periodic performance report generated by the source or sink t1/e1 terminals as defined by ansi t1.403. the other is a path or test signal identification message that may be optionally generated by a terminal or intermediate equipment on a t1/e1 circuit. message-oriented signals shall use the frame structure, field definitions and elements of procedure of the lapd protocol defined in itu recommendation q.921 except the address field. performance information is carried by message-oriented signal using lapd protocol. the message structures of the periodic performance report and path or test signal identification message are shown in figure 128 in format a and format b respectively. 13.1.4.1.1 periodic performance report the ansi t1.403 standard requires that the status of the transmission quality be reported every one-second interval. the one-second timing may be derived from the ds1 signal or from a separate equally accurate (32ppm) source. the phase of the one-second periods with respect to the occurrence of error events is arbitrary; that is, the one-second timing does not depend on the time of occurrence of any error event. a total of four seconds of information is transmitted so that recovery operations may be initiated in case an error corrupts a message. counts of events shall be accumulated in each contiguous one-second interval. at the end of each one-second interval, a modulo-4 counter shall be incremented, and the appropriate performance bits shall be set in bytes 5 and 6 in format a. these octets and the octets that carry the performance bits of the preceding three one- second intervals form the periodic performance report. the periodic performance report is made up of 14 bytes of data. bytes 1 to 4, 13, and 14 are the message header and bytes 5 to 12 contain data regarding the four most-recent one-second intervals. the periodic performance report message uses the sapi/tei value of 14. f igure 128. lapd f rame s tructure 1 2 3 4 5 . . 12 13 14 flag address (high order) address (low order) control information fcs (first octet) fcs (second octet) flag 8 7 6 5 4 3 2 1 octet format a flag 0 1 1 1 1 1 1 0 one-second counts sapi c/r ea 0 tei ea 1 flag 0 1 1 1 1 1 1 0 1 2 3 4 5 . . 80 81 82 flag address (high order) address (low order) control information fcs (first octet) fcs (second octet) flag 8 7 6 5 4 3 2 1 octet format b flag 0 1 1 1 1 1 1 0 76 octets sapi c/r ea 0 tei ea 1 flag 0 1 1 1 1 1 1 0
xrt84l38 399 rev. 1.0.1 octal t1/e1/j1 framer 13.1.4.1.2 transmission-error event occurrences of transmission-error events indicate the quality of transmission. the occurrences that shall be detected and reported are: ? crc error event: a crc-6 error event is the occurrence of a received crc code that is not identical to the corresponding locally calculated code. ? severely errored framing event: a severely-errored-framing event is the occurrence of two or more framing- bit-pattern errors within a 3-ms period. contiguous 3-ms intervals shall be examined. the 3-ms period may coincide with the esf. the severely-errored-framing event, while similar in form to criteria for declaring a terminal has lost framing, is only designed as a performance indicator; existing terminal out-of-frame criteria will continue to serve as the basis for terminal alarms. ? frame-synchronization-bit error event: a frame-synchronization-bit-error event is the occurrence of a received framing-bit-pattern not meeting the severely-errored-framing event criteria. ? line-code violation event: a line-code violation event is a bipolar violation of the incoming data. a line-code violation event for an b8zs-coded signal is the occurrence of a received excessive zeros (exz) or a bipolar violation that is not part of a zero-substitution code. ? controlled slip event: a controlled-slip event is a replication, or deletion, of a t1 frame by the receiving terminal. a controlled slip may occur when there is a difference between the timing of a synchronous receiving terminal and the received signal. 13.1.4.1.3 path and test signal identification message the path identification message is used to identify the path between the source terminal and the sink terminal. the test signal identification message is used by test signal generating equipment. both identification messages are made up of 82 bytes of data. byte 1 to 4, 81 and 82 are the message header and bytes 5 to 80 contain six data elements. these messages use the sapi/tei value of 15 to differentiate themselves from the performance report message. 13.1.4.1.4 frame structure the message structure of message-oriented signal is shown in figure 1?2. two format types are shown in the figure: format a for frames which are sending performance report message and format b for frames which containing a path or test signal identification message. the following abbreviations are used: ? sapi: service access point identifier ? c/r: command or response ? ea: extended address ? tei: terminal endpoint identifier ? fcs: frame check sequence 13.1.4.1.5 flag sequence all frames shall start and end with the flag sequence consisting of one 0 bit followed by six contiguous 1 bits and one 0 bit. the flag preceding the address field is defined as the opening flag. the flag following the frame check sequence (fcs) field is defined as the closing flag. the closing flag may also serve as the opening flag of the next frame, in some applications. however, all receivers must be able to accommodate receipt of one or more consecutive flags. 13.1.4.1.6 address field the address field consists of two octets. a single octet address field is reserved for lapb operation in order to allow a single lapb data link connection to be multiplexed along with lapd data link connections. 13.1.4.1.7 address field extension bit (ea) the address field range is extended by reserving bit 1 of the address field octets to indicate the final octet of the address field. the presence of a 1 in bit 1 of an address field octet signals that it is the final octet of the
xrt84l38 400 octal t1/e1/j1 framer rev. 1.0.1 address field. the double octet address field for lapd operation shall have bit 1 of the first octet set to a 0 and bit 1 of the second octet set to 1. 13.1.4.1.8 command or response bit (c/r) the command or response bit identifies a frame as either a command or a response. the user side shall send commands with the c/r bit set to 0, and responses with the c/r bit set to 1. the network side shall do the opposite; that is, commands are sent with c/r bit set to 1, and responses are sent with c/r bit set to 0. 13.1.4.1.9 service access point identifier (sapi) the service access point identifier identifies a point at which data link layer services are preceded by a data link layer entity type to a layer 3 or management entity. consequently, the sapi specifies a data link layer entity type that should process a data link layer frame and also a layer 3 or management entity, which is to receive information carried by the data link layer frame. the sapi allows 64 service access points to be specified, where bit 3 of the address field octet containing the sapi is the least significant binary digit and bit 8 is the most significant. sapi values are 14 and 15 for performance report message and path or test signal identification message respectively. 13.1.4.1.10 terminal endpoint identifier (tei) the tei sub-field allows 128 values where bit 2 of the address field octet containing the tei is the least significant binary digit and bit 8 is the most significant binary digit. the tei sub-field bit pattern 111 1111 (=127) is defined as the group tei. the group tei is assigned permanently to the broadcast data link connection associated with the addressed service access point (sap). tei values other than 127 are used for the point- to-point data link connections associated with the addressed sap. non-automatic tei values (0-63) are selected by the user, and their allocation is the responsibility of the user. the network automatically selects and allocates tei values (64-126). 13.1.4.1.11 control field the control field identifies the type of frame which will be either a command or response. the control field shall consist of one or two octets. three types of control field formats are specified: 2-octet numbered information transfer (i format), 2-octet supervisory functions (s format), and single-octet unnumbered information transfers and control functions (u format). the control field for t1/e1 message is categorized as a single-octet unacknowledged information transfer having the value 0x03. 13.1.4.1.12 frame check sequence (fcs) field the source of either the performance report or an identification message shall generate the frame check sequence. the fcs field shall be a 16-bit sequence. it shall be the ones complement of the sum (modulo 2) of: ? the remainder of xk (x15 + x14 + x13 + x12 + x11 + x10 + x9 + x8 + x7 + x6 + x5 + x4 + x3 + x2 + x + 1) divided (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, where k is the number of bits in the frame existing between, but not including, the final bit of the opening flag and the first bit of the fcs, excluding bits inserted for transparency, and ? the remainder of the division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, of the product of x16 by the content of the frame existing between, but not including, the final bit of the opening flag and the first bit of the fcs, excluding bits inserted for transparency. as a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all 1s and is then modified by division by the generator polynomial on the address, control and information fields; the ones complement of the resulting remainder is transmitted as the 16-bit fcs. as a typical implementation at the receiver, the initial content of the register of the device computing the remainder is preset to all 1s. the final remainder, after multiplication by x16 and then division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1 of the serial incoming protected bits and the fcs, will be 0001110100001111 (x15 through x0, respectively) in the absence of transmission errors. 13.1.4.1.13 transparency (zero stuffing)
xrt84l38 401 rev. 1.0.1 octal t1/e1/j1 framer a transmitting data link layer entity shall examine the frame content between the opening and closing flag sequences, (address, control, information and fcs field) and shall insert a 0 bit after all sequences of five contiguous 1 bits (including the last five bits of the fcs) to ensure that an idle flag or an abort sequence is not simulated within the frame. a receiving data link layer entity shall examine the frame contents between the opening and closing flag sequences and shall discard any 0 bit which directly follows five contiguous 1 bits. 13.1.4.2 how to configure the transmit hdlc controller block to transmit mos this section describes how to configure the lapd controller block to transmit mos message in a step-by-step basis. 13.1.4.2.1 step 1: find out the next available transmit data link buffer to transmit mos message, the user is recommended to read transmit data link byte count register for next available transmit buffer number. the table below shows how contents of the buffer enable bit of the transmit data link byte count register (tdlbcr) determines what the next available transmit buffer number is. 13.1.4.2.2 step 2: write mos message into transmit data link buffer after finding out the next available transmit buffer, the user should write the entire message data to the available transmit data link buffer via pio or dma access. the writing of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for transmit data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the transmit data link buffer and a microcontroller read will access the receive data link buffers. the very first write access to the lapd buffer indirect data register will always be direct to location 0 within the transmit data link buffer. the next write access to the lapd buffer indirect data register will be direct to location 1 within the transmit data link buffer and so on, until all 96 bytes of the transmit buffer is filled. for example, if the first byte of the mos message to be sent is (01010110) and the next available transmit data link buffer of channel n is 1. the user should write pattern (01010110) into transmit data link buffer 1 of channel n. the following microprocessor access to the framer should be done: wr n7h 56h the first byte of mos message is written into location 0 of the transmit data link buffer. if the next byte of the mos message is (10100101), the user should perform another microprocessor write access: wr n7h a5h the second byte of mos message is written into location 1 of the transmit data link buffer. the write access should be repeated until the entire block of mos message is written into the transmit buffer or the transmit buffer is completely filled. 13.1.4.2.3 step 3: program the transmit data link byte count register the user should program byte count of the mos message into the transmit data link byte count register after the whole block of data is present in the buffer memory. transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it n umber b it n ame b it t ype b it d escription 7 buffer select r 0 - the next available transmit buffer for sending out bos or mos mes - sage is buffer 0. 1 - the next available transmit buffer for sending out bos or mos mes - sage is buffer 1.
xrt84l38 402 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the transmit data link byte count [6:0] bits the transmit data link byte count register (tdlbcr). 13.1.4.2.4 step 4: configure mos message transmission control bits configuration of the data link control register determines whether the lapd controller will insert idle flag character, fcs or abort sequence to the data link channel. it also determines how the transition between mos mode to bos mode is done. if the idle insertion bit of the data link control register is set, repeated flags of value 0x7e are transmitted as soon as the current operation is finished (defined by the value in transmit data link byte count register). the idle bit must be set to 1 at the last block of transfer to enable fcs and flag insertion for message completion. the table below shows configurations of the idle insertion bit of the data link control register (dlcr). n ote : if the entire message is longer than 96-byte in length or more than one full block of message has to be transmitted, the idle insertion bit should not be set to one until the last block of message has to be sent. if the fcs insertion bit of the data link control register (dlcr) is set to high, the lapd controller will calculate and insert the frame check sequence to the last block of the transmitted message. the table below shows configurations of the fcs insertion bit of the data link control register (dlcr). if the fcs is not enabled at the end of a message, the controller will return to sending idle flags immediately after the last octet is transmitted. this permits the use of a programmable fcs, which may be used for diagnostic tests or other test applications. to abort a transmitting message, the lapd controller sets the abort bit in data link control register to 1. this bit is cleared after the lapd transmitter finishes sending the message octet in progress. the transmitter then transmit an abort sequence of one zero followed by seven ones (01111111) before goes to idle if the idle bit is set. the transmitter will keep transmitting idle flag characters until it is instructed otherwise. transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it n umber b it n ame b it t ype b it d escription 6-0 transmit data link byte count [6:0] r/w value of these bits determines length of the mos message pattern to be transmitted by the framer before generating the transmit end of transfer (txeot) interrupt. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 2 idle insertion r/w 0 - no flag sequence is sent on the data link channel. 1 - the framer forces a flag sequence of value 0x7e onto the data link channel. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 1 fcs insertion r/w 0 - no fcs will be inserted into the last block of the transmitted mos mes - sage. 1 - the lapd controller will calculate and insert the fcs into the last block of the transmitted mos message.
xrt84l38 403 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the abort bit of the data link control register (dlcr). switching the data link channel from mos mode to bos mode while a message is being transmitted will interrupt the message after the octet in progress is transmitted. if the mos abort bit of the data link control register is set, a mos abort sequence (a zero followed by 7 ones) will be inserted before switching. switching the data link from bos to lapd will not take place until the current operation completes if transmit bos byte count is not set to zero initially. if the transmit bos byte count value is set to zero, the transition from bos mode to mos mode will take place right after finishing the current message octet. the table below shows configurations of the mos abort bit of the data link control register (dlcr). 13.1.4.2.5 step 5: enable transmit mos message interrupts the lapd controller can generate a couple of interrupts indicating the status of mos message transmission to the microprocessor. these are the transmit start of transfer (txsot) interrupt and the transmit end of transfer (txeot) interrupt. to enable these interrupts, the transmit start of transfer enable bit and the transmit end of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the transmit start of transfer enable bit and the transmit end of transfer enable bit of the data link interrupt enable register. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 3 abort r/w 0 - no abort sequence is sent on the data link channel. 1 - the framer forces an abort sequence of pattern ( 111111 10) onto the data link channel. idle flag pattern will be transmitted after the abort sequence is sent. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 6 mos abort r/w 0 - the framer forces an mos abort sequence of one zero and seven ones [0111 1111] onto the data link ch annel during the transition from mos mode to bos mode. 1 - no mos abort sequence is sent on the data link channel during the transition from mos mode to bos mode. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer enable r/w 0 - the transmit start of transfer interrupt is disabled. 1 - the transmit start of transfer interrupt is enabled. 4 transmit end of transfer enable r/w 0 - the transmit end of transfer interrupt is disabled. 1 - the transmit end of transfer interrupt is enabled.
xrt84l38 404 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the mos message is transmitted to the data link channel, the lapd controller changes the transmit start of transfer and transmit end of transfer status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the transmit start of transfer and transmit end of transfer status bits of the data link status register. 13.1.4.2.6 step 6: mos message transmission a one is then written into the lapd enable bit of data link control register, which sets the transmitter to message-oriented mode and kicks off the transmission process. the lapd controller latches these control bits of the data link control register and send a transmit start of transfer interrupt (txsot) to the microprocessor to indicate that an mos message will be send. the lapd transmitter will then transmit the open flag character (01111110) in the data link bit position first followed by the entire message. if the message is longer than 96 bytes or more than one full block of data are to be transmitted, the alternating buffer usage approach will provide more adequate time to allow the writing of the message in the ping-pong buffers without overwriting good data in the transmitting buffer or repeating data because it was written too late. user must fill in data fast enough in ping-pong buffer concatenation scenario to avoid automatic flag insertion between two blocks of data that will cause far-end fcs errors. after the entire mos message is sent, the lapd controller generates the transmit end of transfer (txeot) interrupt to the microprocessor indicating that the mos message transmission is over. the table below shows configurations of the lapd enable bit of the data link control register (dlcr). block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer rur / wc 0 - there is no data link message to be sent to the data link channel. 1 - the hdlc controller will send a data link message to the data link channel. 4 transmit end of transfer rur / wc 0 - no data link message was sent to the data link channel. 1 - the hdlc controller finished sending a data link message to the data link channel. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 0 lapd enable r/w 0 - the transmit hdlc controller will send out bit-oriented signaling (bos) message. 1 - the transmit hdlc controller will send out lapd protocol or so-called message-oriented signaling (mos) message.
xrt84l38 405 rev. 1.0.1 octal t1/e1/j1 framer 13.1.5 transmit slca96 data link controller the slc?96 t1 format is invented by at&t and is used between the digital switch and a slc?96 formatted remote terminal. the purpose of the slc?96 product is to provide standard telephone service or plain old telephone service (pots) in areas of high subscriber density but back-haul the traffic over t1 facilities. to support the slc?96 formatted remote terminal equipment, which is likely in an underground location, the t1s needed methods to: ? indicate equipment failures of the equipment to maintenance personal ? indicate failures of the pots lines ? test the pots lines ? provide redundancy on the t1s the slc?96 framing format is a d4 super-frame (sf) format with specialized data link information bits. these data link information bits take the position of the super-frame alignment (fs) bit positions. these bits consist of: ? concentrator bits (c, bit position 1 to 11) ? first spoiler bits (fs, bit position 12 to 14) ? maintenance bits (m, bit position 15 to 17) ? alarm bits (a, bit position 18 to 19) ? protection line switch bits (s, bit position 20 to 23) ? second spoiler bit (ss, bit position 24) ? resynchronization pattern (000111000111) in slca96 mode, six six-bit data will generate one 9-ms frame of the slca96 message format. the format of the data link message is given in bellcore tr-tsy-000008. to select this mode, the framing select bits of the framing select register (fsr) must be set to binary number 100. the table below shows configuration of the framing select bits of the framing select register (fsr). framing select register (fsr) (indirect address = 0xn0h, 0x07h) b it n umber b it n ame b it t ype b it d escription 2-0 t1 framing select r/w t1 framing select: these read/write bit-fields allow the user to select one of the five t1 framing formats supported by the framer. these framing formats include esf, slc ? 96, sf, n and t1dm mode. n ote : changing of framing format will automatically force the framer to resync. framing format bit 2 bit 1 bit 0 esf 0 x x slc?96 1 0 0 sf 1 0 1 n 1 1 0 t1dm 1 1 1
xrt84l38 406 octal t1/e1/j1 framer rev. 1.0.1 when slc?96 mode is enabled, the fs bit is replaced by the data link message read from memory at the beginning of each d4 super-frame. the xrt84l38 allocates two 6-byte buffers to provide the slc?96 data link controller an alternating access mechanism for information transmission. the bit ordering and usage is shown in the following table; and the lsb is sent first. note that these registers are memory-based storage and they need to be initialized. each register is read out of memory once every six sf super-frames. the memory holding these registers owns a shared memory structure that is used by multiple devices. these include ds1 transmit module, ds1 receive module, transmit lapd controller, transmit slca96 data link controller, bit-oriented signaling processor, receive lapd controller, receive slca96 data link controller, receive bit-oriented signaling processor and microprocessor interface module. 13.1.5.1 how to configure the slc?96 data link controller to transmit slc?96 data link messages this section describes how to configure the slc?96 data link controller to transmit slc?96 data link message in a step-by-step basis. 13.1.5.1.1 step 1: find out the next available transmit data link buffer to transmit slc?96 data link message, the user is recommended to read transmit data link byte count register for next available transmit buffer number. the table below shows how contents of the buffer enable bit of the transmit data link byte count register (tdlbcr) determines what the next available transmit buffer number is. 13.1.5.1.2 step 2: write slc?96 data link message into transmit data link buffer after finding out the next available transmit buffer, the user should write the entire message data to the available transmit data link buffer via pio or dma access. the writing of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for transmit data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the transmit data link buffer and a microcontroller read will access the receive data link buffers. the very first write access to the lapd buffer indirect data register will always be direct to location 0 within the transmit data link buffer. the transmit slc ? 96 message registers b it b yte 543210 1 0 1 1 1 0 0 2 c1 1 1 1 0 0 3 c7 c6 c5 c4 c3 c2 4 1 0 c11 c10 c9 c8 5 a2 a1 m3 m2 m1 0 6 0 1 s4 s3 s2 s1 transmit data link byte count register (tdlbcr) (indirect address = 0xn0h, 0x14h) b it n umber b it n ame b it t ype b it d escription 7 buffer select r 0 - the next available transmit buffer for sending out bos or mos mes - sage is buffer 0. 1 - the next available transmit buffer for sending out bos or mos mes - sage is buffer 1.
xrt84l38 407 rev. 1.0.1 octal t1/e1/j1 framer next write access to the lapd buffer indirect data register will be direct to location 1 within the transmit data link buffer and so on, until all 96 bytes of the transmit buffer is filled. for example, if the first byte of the slc?96 data link message to be sent is (101011) and the next available transmit data link buffer of channel n is 1. the user should write pattern (00101011) into transmit data link buffer 1 of channel n. the following microprocessor access to the framer should be done: wr n7h 2bh the first byte of the slc?96 data link message is written into location 0 of the transmit data link buffer. if the next byte of the data link message is (101001), the user should perform another microprocessor write access of pattern (00101001): wr n7h 29h the second byte of data link message is written into location 1 of the transmit data link buffer. the write access should be repeated until all six bytes of slc?96 data link message is written into the transmit buffer or the transmit buffer is completely filled. 13.1.5.1.3 step 3: enable transmit data link message interrupt the slc?96 data link controller can generate the transmit start of transfer (txsot) interrupt indicating the status of data link message transmission to the microprocessor. to enable this interrupt, the transmit start of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the transmit start of transfer enable bit of the data link interrupt enable register. the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when this interrupt enable bit is set and the slc?96 data link message is transmitted to the data link channel, the slc?96 data link controller changes the transmit start of transfer status bits of the data link status register (dlsr). this status indicator is valid until the data link status register is read. reading this register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. data link interrupt enable register (dlier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer enable r/w 0 - the transmit start of transfer interrupt is disabled. 1 - the transmit start of transfer interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled.
xrt84l38 408 octal t1/e1/j1 framer rev. 1.0.1 the table below shows the transmit start of transfer and transmit end of transfer status bits of the data link status register. 13.1.5.1.4 step 4: program the data link control register to activate slc?96 data link transmission the slc?96 enable bit and the lapd enable bit of the data link control register (dlcr) determines which one of the three functions is performed by the transmit hdlc controller block. the table below shows configuration of the slc?96 enable bit of the data link control register (dlcr). the table below shows configuration of the lapd enable bit of the data link control register (dlcr). to enable slc?96 data link transmission, the user has to set both of the slc?96 enable bit and the lapd enable bit of the data link control register to 1. without inputting new message, the data link controller will loop on the same message over and over again. to force the data link to output all ones is done by setting the abort bit in data link control register to 1. this operation takes place after the current message finishes transmitting. the table below shows configurations of the abort bit of the data link control register (dlcr). setting the slca96 bit low will switch the data link back to transfer normal framing bits after the current message transmit completes. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 6 transmit start of transfer rur / wc 0 - there is no data link message to be sent to the data link channel. 1 - the slc?96 data link controller will send slc?96 data link message to the data link channel. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 7 slc?96 enable r/w 0 - in slc?96 framing mode, the data link transmission is disabled. the framer transmits the regular sf framing bits. in esf framing mode, the framer transmits regular esf framing bits and facility data link (fdl) bits. 1 - in slc?96 framing mode, the data link transmission is enabled. in esf framing mode, the framer transmits slc?96-like message in the facility data link bits. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 0 lapd enable r/w 0 - the transmit hdlc controller will send out bit-oriented signaling (bos) message. 1 - the transmit hdlc controller will send out lapd protocol or so-called message-oriented signaling (mos) message. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 3 abort r/w 0 - no abort sequence is sent on the data link channel. 1 - the framer forces an abort sequence of pattern ( 111111 10) onto the data link channel.
xrt84l38 409 rev. 1.0.1 octal t1/e1/j1 framer 13.2 ds1 receive hdlc controller block 13.2.1 description of the ds1 receive hdlc controller block xrt84l38 allows user to extract data link information from incoming ds1 frames. the data link information in ds1raming format mode can be extracted to the following: ? ds1 receive overhead output interface block ? ds1 receive hdlc controller ? ds1 receive serial output interface the receive data link source select [1:0] bits, within the receive data link select register (rsdlsr) determine destinations of the data link bits (facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in slc?96 framing format mode and remote signaling (r) bits in t1dm framing format mode) extracted from the incoming ds1 frames. the table below shows configuration of the receive data link source select [1:0] bits of the receive data link select register (rsdlsr). if the receive data link source select bits of the receive data link select register are set to 00, the receive hdlc controller block becomes output destination of the data link bits in incoming ds1 frames. each of the eight framers within the xrt84l38 device contains a ds1 receive high-level data link controller (hdlc) block. the function of this block is to establish a serial data link channel in ds1 mode through the following: ? facility data link (fdl) bits in esf framing format mode ? signaling framing (fs) bits in slc?96 framing format mode ? remote signaling (r) bits in t1dm framing format mode ? d or e signaling timeslot channel data link bits are automatically inserted into the facility data link (fdl) bits in esf framing format mode, signaling framing (fs) bits in slc?96 framing format mode and remote signaling (r) bits in t1dm framing format mode or forced to 1 by the framer. additionally, xrt84l38 allows the user to define any one of ones of the twenty-four ds0 timeslots to be d or e channel. we will discuss how to configure xrt84l38 to receive data link information through d or e channels in later section. the ds1 receive hdlc controller block contains three major functional modules associated with ds1 framing formats. they are the: ? slc?96 data link controller ? lapd controller ? bit-oriented signaling processor. receive data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 1-0 receive data link source select [1:0] r/w 00 - the data link bits extracted from the incoming ds1 frame are sent to the receive hdlc controller. 01 - the data link bits extracted from the incoming ds1 frame are sent to the receive serial data output interface via the rxser_n pins. 10 - the data link bits extracted from the incoming ds1 frame are sent to the receive overhead output interface via the rxoh_n pins. 11 - the data link bits are forced into 1.
xrt84l38 410 octal t1/e1/j1 framer rev. 1.0.1 there are two 96-byte receive message buffer in shared memory for each of the eight framers to receive data link information. when one message buffer is filled up, the ds1 receive hdlc controller automatically switches to the next message buffer to store data link messages. these two message buffers ping-pong among each other for data link message storage. the slc?96 enable bit and the message type bit of the data link status register (dlsr) determines which one of the three messages is received and processed by the receive hdlc controller block. the table below shows configuration of the slc?96 enable bit of the data link control register (dlcr). the table below shows configuration of the message type bit of the data link status register (dlsr). 13.2.2 how to configure xrt84l38 to receive data link information through d or e channels the xrt84l38 can configure any one or ones of the twenty-four ds0 channels to be d or e channels. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the receive conditioning select [3:0] bits of the receive channel control register (rccr) of each channel determine whether that particular channel is configured as d or e channel. these bits also determine what type of data or signaling conditioning is applied to each channel. if the receive conditioning select [3:0] bits of the receive channel control register of a particular timeslot are set to 1111, that timeslot is configured as a d or e timeslot. any d or e timeslot can be configured to direct data link information to the following destinations: ? ds1 receive overhead output interface block ? ds1 receive hdlc controller block ? ds1 receive serial output interface block data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 7 slc?96 enable r/w 0 - in slc?96 framing mode, the data link transmission is disabled. the framer receives the regular sf framing bits. in esf framing mode, the framer receives regular esf framing bits and facility data link (fdl) bits. 1 - in slc?96 framing mode, the data link transmission is enabled. in esf framing mode, the framer receives slc?96-like message in the facility data link bits. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 7 message type rur / wc 0 - the receive hdlc controller receives and processes bit-oriented signaling (bos) message. 1 - the receive hdlc controller receives and processes lapd protocol or message-oriented signaling (mos) message. receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it n umber b it n ame b it t ype b it d escription 3-0 receive condition - ing select r/w 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 411 rev. 1.0.1 octal t1/e1/j1 framer ? ds1 receive fractional output interface block the receive d or e channel source select [1:0] bits of the receive data link select register (rsdlsr) determines which one of the above-mentioned modules to be output destinations of d or e timeslot. the table below shows configuration of the receive d or e channel source select [1:0] bits of the receive data link select register (rsdlsr). for the receive hdlc controller to be output destination of d or e channel, the receive d or e channel source select [1:0] bits of the receive data link select register has to be set to 01. 13.2.3 receive bos (bit oriented signaling) processor the receive bos processor handles receiving and processing of bos messages through the ds1 data link channel. it generates receive end of transfer (rxeot) interrupt each time a bos message is received and stores the bos message into the receive message buffer. in the later section, we will discuss how to configure the bos processor block to receive bos message. 13.2.3.1 how to configure the bos processor block to receive bos this section describes how to configure the bos processor block to receive bos message and how to read out the bos message. the operation of the receive bos processor is interrupt-driven. when a bos message is received, message octet is written to the next receive data link message buffer opposite to that last used. the receive bos processor generates interrupts to the microprocessor notifying it that a bos message is received. the bos message can then be extracted from the appropriate receive data link buffer. 13.2.3.1.1 step 1: enable receive bos message interrupts the bos processor can generate a couple of interrupts indicating the status of bos message received to the microprocessor. these are the receive start of transfer (rxsot) interrupt and the receive end of transfer (rxeot) interrupt. to enable these interrupts, the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register. receive data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 3-2 receive d or e channel source select [1:0] r/w 00 - the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive serial data output interface via the rxser_n pins. 01 - the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive hdlc controller. 10 - the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive fractional t1 output interface via the rxfrt1_n pins. 11 - the data link bits extracted form the d or e channel of incoming ds1 frame are inserted into the receive serial data output interface via the rxser_n pins. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer enable r/w 0 - the receive start of transfer interrupt is disabled. 1 - the receive start of transfer interrupt is enabled.
xrt84l38 412 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the bos message is received in the data link channel, the bos processor changes the receive start of transfer and receive end of transfer status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive start of transfer and receive end of transfer status bits of the data link status register. the bos processor can also generate interrupts when either the bos abort sequence (nine consecutive ones) or the idle flag character (hexadecimal value of 0x7eh) is received in the data link channel to the microprocessor. these are the receive abort sequence (rxabort) interrupt and the receive idle flag sequence (rxidle) interrupt. to enable these interrupts, the receive abort sequence enable bit and the receive idle flag sequence enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive abort sequence enable bit and the receive idle flag sequence enable bit of the data link interrupt enable register. 3 receive end of transfer enable r/w 0 - the receive end of transfer interrupt is disabled. 1 - the receive end of transfer interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer rur / wc 0 - there is no data link message in the data link channel. 1 - the hdlc controller began to receive a data link message in the data link channel. 3 receive end of transfer rur / wc 0 - no data link message was present in the data link channel. 1 - the hdlc controller finished receiving a data link message in the data link channel. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence enable r/w 0 - the receive abort sequence interrupt is disabled. 1 - the receive abort sequence interrupt is enabled. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription
xrt84l38 413 rev. 1.0.1 octal t1/e1/j1 framer when these interrupt enable bits are set and the bos abort sequence or idle flag sequence is received in the data link channel, the bos processor changes the receive abort sequence and receive idle flag sequence status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive abort sequence and receive idle flag sequence status bits of the data link status register. 13.2.3.1.2 step 2: find out the next available receive data link buffer to transmit a bit-oriented signal, a repeating message is sent of the form (0d5d4d3d2d1d00 11111111), where the "d5d4d3d2d1d0" represents a six-bit message. when receiving a bos message, the received message octet is written to the next available receive data link buffer in the form of (0d5d4d3d2d1d00). the user is recommended to read receive data link byte count register for next available receive data link buffer number. the table below shows how contents of the receive buffer pointer bit of the receive data link byte count register (rdlbcr) determines what the next available receive data link buffer number is. 13.2.3.1.3 step 3: program bos message receiving repetitions the user should program the value of message receiving repetitions into the receive data link byte count register. the framer will receive the bos message the same number of times as was stored in the receive data link byte count register (rdlbcr) before generating the receive end of transfer (rxeot) interrupts. if the value stored inside the receive data link byte count register (rdlbcr) is set to 0, the message will be received indefinitely and no receive end of transfer interrupt will be generated. the table below shows configurations of the receive data link byte count [6:0] bits the receive data link byte count register (rdlbcr). 0 receive idle flag sequence enable r/w 0 - the receive idle flag sequence interrupt is disabled. 1 - the receive idle flag sequence interrupt is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence rur / wc 0 - there is no bos abort sequence received in the data link channel. 1 - the hdlc controller receives bos abort sequence in the data link channel. 0 receive idle flag sequence rur / wc 0 - the message received in the data link channel is bos message. 1 - the message received in the data link channel is mos message. receive data link byte count register (rdlbcr) (indirect address = 0xn0h, 0x15h) b it n umber b it n ame b it t ype b it d escription 7 receive buffer pointer r 0 - the next available receive data link buffer for reading out bos or mos message is buffer 0. 1 - the next available receive data link buffer for reading out bos or mos message is buffer 1. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription
xrt84l38 414 octal t1/e1/j1 framer rev. 1.0.1 13.2.3.1.4 step 4: read bos message from receive data link buffer upon detection of the receive end of transfer (rxeot) interrupt, the user should read the message type bit of the data link status register (dlsr) to find out what is the type of message received. the table below shows how contents of the message type bit of the data link status register (dlsr) determines what the type of message received in the data link channel is. after determined that the received message is a bos one, the use should read eight bits message from the first location of the next available receive data link buffer. the reading of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for receive data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the receive data link buffer and a microcontroller read will access the receive data link buffers. the very first read access to the lapd buffer indirect data register will always be direct to location 0 within the receive data link buffer. for example, if the bos message to received is (101011) and the next available receive data link buffer of channel n is 1. the user should be able to read pattern (01010110) from receive data link buffer 1 of channel n. the following microprocessor access to the framer should be done: rd n7h the result of the read access should be 0x56h. 13.2.4 receive lapd controller the receive lapd controller implements the message-oriented protocol based on itu recommendation q.921 link access procedures on the d-channel (lapd) type of protocol. it provides the following functions: ? zero deletion ? pattern recognition for idle flag detection ? pattern recognition for abort sequence detection ? frame check sequence verification ? t1 receiver interface ? receive data link message buffer access receive data link byte count register (rdlbcr) (indirect address = 0xn0h, 0x15h) b it n umber b it n ame b it t ype b it d escription 6-0 receive data link byte count [6:0] r/w value of these bits determines how many times a bos message pattern will be received by the framer before generating the receive end of trans - fer (txeot) interrupt. n ote : if these bits are set to 0, the bos message will be received indefinitely and no receive end of transfer interrupts will be generated. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 7 message type rur / wc 0 - there is no bos abort sequence received in the data link channel. 1 - the hdlc controller receives bos abort sequence in the data link channel.
xrt84l38 415 rev. 1.0.1 octal t1/e1/j1 framer two 96-byte buffers in shared memory are allocated for receive lapd controller to reduce the frequency of microprocessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt. there are no restrictions on the length of the message received. however, the 96-byte buffer is deep enough to hold one entire lapd path or test signal identification message. the following section discuss how to configure the receive lapd controller to receive and extract mos messages. 13.2.4.1 how to configure the receive hdlc controller block to receive mos message this section describes how to configure the lapd controller block to receive and extract mos message in a step-by-step basis. the operation of the receive lapd controller is interrupt-driven. when an mos message is receiving, message octets are written to the next receive data link message buffer opposite to that last used. each time the receiving data link message buffer is filled, a rxeot interrupt is issued if it is enabled. this process continues until an abort sequence is received or an idle flag is received. an interrupt is issued when one of the following conditions occurs and the corresponding interrupt enable bit is set. ? the rxsot is set when the beginning of a data link message is received (the first non-flag message). ? the rxeot is set when the end of a data link block is received. ? the rxidle is set if an idle flag sequence (b01111110) is received on the data link after either an abort sequence is received or a complete message is received. ? the rxabort is set when an abort sequence is received. ? the fcs_err is issued when an erroneous frame check sequence is detected at the end of a message or an idle flag is received that is not octet aligned. 13.2.4.1.1 step 1: enable receive mos message interrupts the receive lapd controller can generate a couple of interrupts indicating the status of mos message received to the microprocessor. these are the receive start of transfer (rxsot) interrupt and the receive end of transfer (rxeot) interrupt. to enable these interrupts, the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer enable r/w 0 - the receive start of transfer interrupt is disabled. 1 - the receive start of transfer interrupt is enabled. 3 receive end of transfer enable r/w 0 - the receive end of transfer interrupt is disabled. 1 - the receive end of transfer interrupt is enabled.
xrt84l38 416 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the mos message is received in the data link channel, the lapd controller changes the receive start of transfer and receive end of transfer status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive start of transfer and receive end of transfer status bits of the data link status register. the lapd controller can also generate interrupts when either the mos abort sequence (seven consecutive ones) or the idle flag character (hexadecimal value of 0x7eh) is received in the data link channel to the microprocessor. these are the receive abort sequence (rxabort) interrupt and the receive idle flag sequence (rxidle) interrupt. to enable these interrupts, the receive abort sequence enable bit and the receive idle flag sequence enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the receive abort sequence enable bit and the receive idle flag sequence enable bit of the data link interrupt enable register. when these interrupt enable bits are set and the mos abort sequence or idle flag sequence is received in the data link channel, the lapd controller changes the receive abort sequence and receive idle flag sequence status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer rur / wc 0 - there is no data link message in the data link channel. 1 - the hdlc controller began to receive a data link message in the data link channel. 3 receive end of transfer rur / wc 0 - no data link message was present in the data link channel. 1 - the hdlc controller finished receiving a data link message in the data link channel. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence enable r/w 0 - the receive abort sequence interrupt is disabled. 1 - the receive abort sequence interrupt is enabled. 0 receive idle flag sequence enable r/w 0 - the receive idle flag sequence interrupt is disabled. 1 - the receive idle flag sequence interrupt is enabled.
xrt84l38 417 rev. 1.0.1 octal t1/e1/j1 framer selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive abort sequence and receive idle flag sequence status bits of the data link status register. finally, the lapd controller generates frame check sequence error (fcs_err) interrupt when an erroneous frame check sequence is detected at the end of a message or an idle flag is received that is not octet aligned. to enable this interrupt, the frame check sequence error detection enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. the table below shows configurations of the frame check sequence error detection enable bit of the data link interrupt enable register. when the frame check sequence error detection interrupt enable bits is set and an erroneous frame check sequence is detected at the end of a message, the lapd controller changes the frame check sequence error detection status bits of the data link status register (dlsr). this status indicator is valid until the data link status register is read. reading this register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset this status indicator. the table below shows the frame check sequence error detection status bits of the data link status register. 13.2.4.1.2 step 2: find out the next available receive data link buffer when the lapd controller is receiving mos message, the received message octets are written to the next available receive data link buffer. the user is recommended to read receive data link byte count register for next available receive data link buffer number. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence rur / wc 0 - there is no bos abort sequence received in the data link channel. 1 - the hdlc controller receives mos abort sequence in the data link channel. 0 receive idle flag sequence rur / wc 0 - the message received in the data link channel is bos message. 1 - the message received in the data link channel is mos message. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 2 frame check sequence error detection enable r/w 0 - the frame check sequence error detection interrupt is disabled. 1 - the frame check sequence error detection interrupt is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 2 frame check sequence error detection rur / wc 0 - there is no fcs error detected in the data link channel. 1 - the hdlc controller receives an erroneous fcs in the data link chan - nel.
xrt84l38 418 octal t1/e1/j1 framer rev. 1.0.1 the table below shows how contents of the receive buffer pointer bit of the receive data link byte count register (rdlbcr) determines what the next available receive data link buffer number is. 13.2.4.1.3 step 3: reading the receive data link byte count register the user should read the length of mos message from the receive data link byte count register. the receive lapd controller increments the receive data link byte count register value when each octet of mos message is received. after the receive end of transfer (rxeot) interrupt is generated, the receive data link byte count register should contain the length of entire mos message. the table below shows configurations of the receive data link byte count [6:0] bits of the receive data link byte count register (rdlbcr). 13.2.4.1.4 step 4: read mos message from receive data link buffer upon detection of the receive end of transfer (rxeot) interrupt, the user should read the message type bit of the data link status register (dlsr) to find out what is the type of message received. the table below shows how contents of the message type bit of the data link status register (dlsr) determines what the type of message received in the data link channel is. after determined that the received message is an mos one, the use should read the entire message from the available receive data link buffer. the reading of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for receive data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the receive data link buffer and a microcontroller read will access the receive data link buffers. the very first read access to the lapd buffer indirect data register will always be direct to location 0 within the receive data link buffer. for example, if the first octet of the mos message received is (10101100) and the next available receive data link buffer of channel n is 1. the user should be able to read pattern (01010110) from receive data link buffer 1 of channel n. the following microprocessor access to the framer should be done: rd n7h receive data link byte count register (rdlbcr) (indirect address = 0xn0h, 0x15h) b it n umber b it n ame b it t ype b it d escription 7 receive buffer pointer r 0 - the next available receive data link buffer for reading out bos or mos message is buffer 0. 1 - the next available receive data link buffer for reading out bos or mos message is buffer 1. receive data link byte count register (rdlbcr) (indirect address = 0xn0h, 0x15h) b it n umber b it n ame b it t ype b it d escription 6-0 receive data link byte count [6:0] r value of these bits determines how many times a bos message pattern will be received by the framer before generating the receive end of trans - fer (txeot) interrupt. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 7 message type rur / wc 0 - message received in the data link channel is bos. 1 - message received in the data link channel is mos.
xrt84l38 419 rev. 1.0.1 octal t1/e1/j1 framer the result of the read access should be 0xach. 13.2.5 receive slca96 data link controller this section describes how to configure the receive slc?96 data link controller block to receive slc?96 data link message and how to read out the message from the receive data link message buffer. the operation of the receive slc?96 data link controller is interrupt-driven. when a 36-bit slc?96 data link message is received, message octet is written to the next receive data link message buffer opposite to that last used. the receive slc?96 data link controller generates interrupts to the microprocessor notifying it that a message is received. the data link message can then be extracted from the appropriate receive data link buffer. in order to enable this mode of operation, the framing mode must be set to slc?96. the xrt84l38 allocates two 6-byte buffers to provide slc?96 data link controller an alternating access mechanism for information received. the bit ordering and usage is shown in the following table. the bits 7 and 6 are forced to 0 by the slc?96 data link controller. 13.2.5.1 how to configure the slc?96 data link controller to receive slc?96 data link messages this section describes how to configure the slc?96 data link controller to receive slc?96 data link message in a step-by-step basis. the operation of the receive slc?96 data link controller is interrupt-driven. when an slc?96 data link message is receiving, message octets are written to the next receive data link message buffer opposite to that last used. every time the slc?96 data link controller receives a 36-bit slc?96 data link message, an rxeot interrupt is issued if it is enabled. this process continues until an abort sequence is received. an interrupt is issued when one of the following conditions occurs and the corresponding interrupt enable bit is set. ? the rxsot is set when the beginning of a data link message is received. ? the rxeot is set when the end of a data link block is received. ? the rxabort is set when an abort sequence is received. 13.2.5.1.1 step 1: enable receive slc?96 data link message interrupts the receive slc?96 data link controller can generate a couple of interrupts indicating the status of slc?96 message received to the microprocessor. these are the receive start of transfer (rxsot) interrupt and the receive end of transfer (rxeot) interrupt. to enable these interrupts, the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. receive slc ? 96 message registers b it b yte 76543210 1/7 0 0 0 1 1 1 0 0 2/8 0 0 c1 1 1 1 0 0 3/9 0 0 c7 c6 c5 c4 c3 c2 4/10 0 0 1 0 c11 c10 c9 c8 5/11 0 0 a2 a1 m3 m2 m1 0 6/12 0 0 0 1 s4 s3 s2 s1
xrt84l38 420 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configurations of the receive start of transfer enable bit and the receive end of transfer enable bit of the data link interrupt enable register. the table below shows configurations of the hdlc controller interrupt enable bit of the block interrupt enable register. when these interrupt enable bits are set and the slc?96 message is received in the data link channel, the slc?96 data link controller changes the receive start of transfer and receive end of transfer status bits of the data link status register (dlsr). these two status indicators are valid until the data link status register is read. reading these register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive start of transfer and receive end of transfer status bits of the data link status register. the slc?96 data link controller can also generate interrupts when the abort sequence is received in the data link channel to the microprocessor. this is the receive abort sequence (rxabort). to enable this interrupt, the receive abort sequence enable bit of the data link interrupt enable register (dlier) have to be set. in addition, the hdlc controller interrupt enable bit of the block interrupt enable register (bier) needs to be one. data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer enable r/w 0 - the receive start of transfer interrupt is disabled. 1 - the receive start of transfer interrupt is enabled. 3 receive end of transfer enable r/w 0 - the receive end of transfer interrupt is disabled. 1 - the receive end of transfer interrupt is enabled. block interrupt enable register (bier) (indirect address = 0xnah, 0x00h) b it n umber b it n ame b it t ype b it d escription 3 hdlc controller interrupt enable r/w 0 - every interrupt generated by the hdlc controller is disabled. 1 - every interrupt generated by the hdlc controller is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 5 receive start of transfer rur / wc 0 - there is no data link message in the data link channel. 1 - the slc?96 data link controller began to receive a data link message in the data link channel. 3 receive end of transfer rur / wc 0 - no data link message was present in the data link channel. 1 - the slc?96 data link controller finished receiving a data link mes - sage in the data link channel.
xrt84l38 421 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configurations of the receive abort sequence enable bit and the receive idle flag sequence enable bit of the data link interrupt enable register. when these interrupt enable bits are set and the slc?96 abort sequence is received in the data link channel, the slc?96 data link controller changes the receive abort sequence status bit of the data link status register (dlsr). this status indicator is valid until the data link status register is read. reading the register clears the associated interrupt if reset upon read is selected in interrupt control register (icr). otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. the table below shows the receive abort sequence status bit of the data link status register. 13.2.5.1.2 step 2: find out the next available receive data link buffer when the slc?96 data link controller is receiving slc?96 message, the received message octets are written to the next available receive data link buffer. the user is recommended to read receive data link byte count register for next available receive data link buffer number. the table below shows how contents of the receive buffer pointer bit of the receive data link byte count register (rdlbcr) determines what the next available receive data link buffer number is. 13.2.5.1.3 step 3: read slc?96 data link message from receive data link buffer upon detection of the receive end of transfer (rxeot) interrupt, the use should read the entire slc?96 data link message from the available receive data link buffer. the reading of these buffers is through the lapd buffer 0 indirect data registers and the lapd buffer1 indirect data registers. lapd buffer 0 and 1 indirect data registers have addresses 0xn6h and 0xn7h respectively. there is no indirect address register for receive data link buffer 0 and 1. a microcontroller write access to the lapd buffer indirect data registers will access the receive data link buffer and a microcontroller read will access the receive data link buffers. the very first read access to the lapd buffer indirect data register will always be direct to location 0 within the receive data link buffer. for example, if the first octet of the slc?96 message received is (00101011) and the next available receive data link buffer of channel n is 1. the user should be able to read pattern (00101011) from receive data link buffer 1 of channel n. the following microprocessor access to the framer should be done: data link interrupt enable register (d lier) (indirect address = 0xnah, 0x07h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence enable r/w 0 - the receive abort sequence interrupt is disabled. 1 - the receive abort sequence interrupt is enabled. data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 1 receive abort sequence rur / wc 0 - there is no bos abort sequence received in the data link channel. 1 - the slc?96 data link controller receives abort sequence in the data link channel. receive data link byte count register (rdlbcr) (indirect address = 0xn0h, 0x15h) b it n umber b it n ame b it t ype b it d escription 7 receive buffer pointer r 0 - the next available receive data link buffer for reading out data link mes - sage is buffer 0. 1 - the next available receive data link buffer for reading out data link mes - sage is buffer 1.
xrt84l38 422 octal t1/e1/j1 framer rev. 1.0.1 rd n7h the result of the read access should be 0x2bh.
xrt84l38 423 rev. 1.0.1 octal t1/e1/j1 framer 14.0 e1 hdlc controller block 14.1 e1 transmit hdlc controller block 14.1.1 description of the e1 transmit hdlc controller block xrt84l38 allows user to insert data link information to outbound e1 frames. the data link information in e1 framing format mode can be inserted from: ? e1 transmit overhead input interface block ? e1 transmit hdlc controller ? e1 transmit serial input interface the transmit data link source select [1:0] bits, within the synchronization mux register (smr) determine source of the data link bits to be inserted into the outgoing e1 frames. the table below shows configuration of the transmit data link source select [1:0] bits of the synchronization mux register (smr). if the transmit data link source select bits of the transmit data link select register are set to 01, the transmit hdlc controller block becomes input source of the data link bits in outgoing e1 frames. each of the eight framers within the xrt84l38 device contains an e1 transmit high-level data link controller (hdlc) block. the function of this block is to provide a serial data link channel in e1 mode through the following: ? the national bits (sa4 through sa8) of timeslot 0 of non-fas frame ? timeslot 16 octet when the framer is in common channel signaling mode ? d or e signaling timeslot channel we will discuss how to configure xrt84l38 to transmit data link information through each of these data link channels in later sections. the e1 transmit hdlc controller block contains two major functional modules associated with e1 framing formats. they are the lapd controller and the bit-oriented signaling processor. there are two 96-byte transmit message buffers in shared memory for each of the eight framers to transmit data link information. when one message buffer is filled up, the transmit hdlc controller automatically switches to the next message buffer to load data link messages. these two message buffers ping-pong among each other for data link message transmission. the lapd enable bit of the data link control register (dlcr) determines whether the transmit hdlc controller block should perform as the lapd controller or the bos processor. synchronization mux register (smr) (indirect address = 0xn0h, 0x09h) b it n umber b it n ame b it t ype b it d escription 3-2 transmit data link source select [1:0] r/w 00 - the data link bits are inserted into the framer through the transmit serial data input interface via the txser_n pins. 01 - the data link bits are inserted into the framer through the transmit hdlc controller. 10 - the data link bits are inserted into the framer through the transmit overhead input interface via the txoh_n pins. 11 - the data link bits are inserted into the framer through the transmit serial data input interface via the txser_n pins.
xrt84l38 424 octal t1/e1/j1 framer rev. 1.0.1 the table below shows configuration of the lapd enable bit of the data link control register (dlcr). 14.1.2 how to configure xrt84l38 to transmit data link information through the national bits (sa4 through sa8) as mentioned in previous section, the national bits (sa4 through sa8) of timeslot 0 of non-fas frame can be used to transmit data link information in e1 mode. the xrt84l38 allows the user to decide on the following: ? whether the national bits will be used to carry the data link information bits. ? how many of the national bits will be used to carry the data link information bits. ? which of these national bits will be used to carry the data link information bits. the transmit signaling and data link control [2:0] bits of the transmit signaling and data link select register (tsdlsr) determines if the national bits will be used to carry data link information. the table below shows configuration of the transmit signaling and data link control [2:0] bits of the transmit signaling and data link select register (tsdlsr). if the transmit signaling and data link select [2:0] bits of the transmit signaling and data link select register is set to 000 or 001, the data link interface becomes source of the sa4 through sa8 national bits. the transmit sa data link select bits of the transmit signaling and data link select register (tsdlsr) determine which ones of the national bits are configured as data link bits in e1 framing format mode. depending upon the configuration of the transmit signaling and data link select register, either of the following cases may exists: ? none of the national bits are used to transport the data link information bits (that is, data link channel of xrt84l38 is inactive). ? any combination of between 1 and all 5 of the national bits can be selected to transport the data link information bits. data link control register (dlcr) (indirect address = 0xn0h, 0x13h) b it n umber b it n ame b it t ype b it d escription 0 lapd enable r/w 0 - the transmit hdlc controller will send out bit-oriented signaling (bos) message. 1 - the transmit hdlc controller will send out lapd protocol or so-called message-oriented signaling (mos) message. transmit signaling and data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 2-0 transmit signaling and data link select r/w 000 - the data link interface is source of the sa4 through sa8 nation bits. 001 - the data link interface is source of the sa4 through sa8 nation bits. 010 - the sa4 through sa8 nation bits are forced to 1. 011 - the sa4 through sa8 nation bits are forced to 1. 1xx - the sa4 through sa8 nation bits are forced to 1.
xrt84l38 425 rev. 1.0.1 octal t1/e1/j1 framer the table below shows configuration of the transmit sa data link select bits of the transmit signaling and data link select register (tsdlsr). 14.1.3 how to configure xrt84l38 to transmit data link information through timeslot 16 octet in e1 mode, timeslot 16 octet can be configured to transmit the following: ? channel associated signaling (cas) bits a, b, c and d ? common channel signaling (ccs) bits the common channel signaling (ccs) messages are actually data link information applicable to all thirty-two timeslots of an e1 frame, thus the name common channel signaling. the transmit signaling and data link control [2:0] bits of the transmit signaling and data link select register (tsdlsr) determine if timeslot octet will be used to carry data link information or cas signals. the table below shows configuration of the transmit signaling and data link control [2:0] bits of the transmit signaling and data link select register (tsdlsr). if the transmit signaling and data link select [2:0] bits of the transmit signaling and data link select register are set to 1xx, the data link interface becomes source of the timeslot 16 octet. 14.1.4 how to configure xrt84l38 to transmit data link information through d or e channels transmit signaling and data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 7 transmit sa8 data link select r/w 0 - source of the sa8 nation bit is not from the data link interface. 1 - source the sa8 national bit from the data link interface. 6 transmit sa7 data link select r/w 0 - source of the sa7 nation bit is not from the data link interface. 1 - source the sa7 national bit from the data link interface. 5 transmit sa6 data link select r/w 0 - source of the sa6 nation bit is not from the data link interface. 1 - source the sa6 national bit from the data link interface. 4 transmit sa5 data link select r/w 0 - source of the sa5 nation bit is not from the data link interface. 1 - source the sa5 national bit from the data link interface. 3 transmit sa4 data link select r/w 0 - source of the sa4 nation bit is not from the data link interface. 1 - source the sa4 national bit from the data link interface. transmit signaling and data link select register (tsdlsr) (indirect address = 0xn0h, 0x0ah) b it n umber b it n ame b it t ype b it d escription 2-0 transmit signaling and data link select r/w 000 - timeslot 16 octet is taken directly from the transmit serial input interface through the txser_n pin. 001 - timeslot 16 octet is taken directly from the transmit overhead input interface through the txoh_n pin or the transmit signaling control regis - ter of timeslot 16. 010 - timeslot 16 octet is taken directly from the transmit serial input interface through the txser_n pin. 011 - timeslot 16 octet is taken directly from the transmit overhead input interface through the txoh_n pin or the transmit signaling control regis - ter of timeslot 16. 1xx - timeslot 16 octet is taken from the data link interface.
xrt84l38 426 octal t1/e1/j1 framer rev. 1.0.1 the xrt84l38 can configure any one or ones of the thirty-two e1 channels to be d or e channels except for channel number 0. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the transmit conditioning select [3:0] bits of the transmit channel control register (tccr) of each channel determine whether that particular channel is configured as d or e channel. these bits also determine what type of data or signaling conditioning is applied to each channel. if the transmit conditioning select [3:0] bits of the transmit channel control register of a particular timeslot are set to 1111, that timeslot is configured as a d or e timeslot. n ote : timeslot 0 can never be configured as d or e timeslot. 14.1.5 transmit bos (bit oriented signaling) processor the transmit bos processor handles transmission of bos messages through the e1 data link channel. it determines how many repetitions a certain bos message will be transmitted. it also inserts bos idle flag sequence and abort sequence to be transmitted on the data link channel. please see section ? for descriptions of bos message format and how to transmit bos message. 14.1.6 transmit mos (message oriented signaling) or lapd controller the transmit lapd controller implements the message-oriented protocol based on itu recommendation q.921 link access procedures on the d-channel (lapd) type of protocol. it provides the following functions: ? zero stuffing ? t1/e1 transmitter interface ? transmit message buffer access ? frame check sequence generation ? idle flag insertion ? abort sequence generation two 96-byte buffers in shared memory are allocated for lapd transmitter to reduce the frequency of microprocessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt. there are no restrictions on the length of the message. however the 96-byte buffer is deep enough to hold one entire lapd path or test signal identification message. please see section ? for descriptions of mos message format and how to configure the lapd controller to transmit mos message. 14.2 e1 receive hdlc controller block 14.2.1 description of the e1 receive hdlc controller block xrt84l38 detects and extracts data link information from incoming e1 frames. the data link information in e1 framing format mode can be extracted to: ? e1 receive overhead output interface block ? e1 receive hdlc controller ? e1 receive serial output interface the extracted data link information is routed to the e1 receive overhead output interface and the e1 receive serial output interface no matter whether the e1 receive hdlc controller module is activated or not. transmit channel control register (tccr) (indirect address = 0xn2h, 0x00h - 0x1fh) b it n umber b it n ame b it t ype b it d escription 3-0 transmit condi - tioning select r/w 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 427 rev. 1.0.1 octal t1/e1/j1 framer each of the eight framers within the xrt84l38 device contains an e1 receive high-level data link controller (hdlc) block. the function of this block is to establish a serial data link channel in e1 mode through the following: ? the national bits (sa4 through sa8) of timeslot 0 of non-fas frame ? timeslot 16 octet when the framer is in common channel signaling mode ? d or e signaling timeslot channel we will discuss how to configure xrt84l38 to transmit data link information through each of these data link channels in later sections. the e1 transmit hdlc controller block contains two major functional modules associated with e1 framing formats. they are the lapd controller and the bit-oriented signaling processor. there are two 96-byte receive message buffer in shared memory for each of the eight framers to receive data link information. when one message buffer is filled up, the e1 receive hdlc controller automatically switches to the next message buffer to store data link messages. these two message buffers ping-pong among each other for data link message storage. the message type bit of the data link status register (dlsr) determines which one of the three messages is received and processed by the receive hdlc controller block. the table below shows configuration of the message type bit of the data link status register (dlsr). 14.2.2 how to configure xrt84l38 to receive data link information through the national bits (sa4 through sa8) as mentioned in previous section, the national bits (sa4 through sa8) of timeslot 0 of non-fas frame can be used to receive data link information in e1 mode. the xrt84l38 allows the user to decide on the following: ? whether the national bits will be used to carry the data link information bits. ? how many of the national bits will be used to carry the data link information bits. ? which of these national bits will be used to carry the data link information bits. the receive signaling and data link control [2:0] bits of the receive signaling and data link select register (rsdlsr) determines if the national bits will be used to carry data link information. the table below shows data link status register (dlsr) (indirect address = 0xnah, 0x06h) b it n umber b it n ame b it t ype b it d escription 7 message type rur / wc 0 - the receive hdlc controller receives and processes bit-oriented signaling (bos) message. 1 - the receive hdlc controller receives and processes lapd protocol or message-oriented signaling (mos) message.
xrt84l38 428 octal t1/e1/j1 framer rev. 1.0.1 configuration of the receive signaling and data link control [2:0] bits of the receive signaling and data link select register (rsdlsr). if the receive signaling and data link select [2:0] bits of the receive signaling and data link select register are set to 000 or 001, the data link interface becomes destination of the sa4 through sa8 national bits. the receive sa data link select bits of the receive signaling and data link select register (rsdlsr) determine which ones of the national bits are configured as data link bits in e1 framing format mode. depending upon the configuration of the receive signaling and data link select register, either of the following cases may exists: ? none of the national bits are used to transport the data link information bits (that is, data link channel of xrt84l38 is inactive). ? any combination of between 1 and all 5 of the national bits can be selected to transport the data link information bits. the table below shows configuration of the receive sa data link select bits of the receive signaling and data link select register (rsdlsr). 14.2.3 how to configure xrt84l38 to receive data link information through timeslot 16 octet in e1 mode, timeslot 16 octet can be configured to receive the following: ? channel associated signaling (cas) bits a, b, c and d ? common channel signaling (ccs) bits receive signaling and data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 2-0 receive signaling and data link select r/w 000 - the data link interface is destination of the sa4 through sa8 nation bits. 001 - the data link interface is destination of the sa4 through sa8 nation bits. 010 - the sa4 through sa8 nation bits are forced to 1. 011 - the sa4 through sa8 nation bits are forced to 1. 1xx - the sa4 through sa8 nation bits are forced to 1. receive signaling and data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 7 receive sa8 data link select r/w 0 - destination of the sa8 nation bit is not the data link interface. 1 - destination of the sa8 national bit is the data link interface. 6 receive sa7 data link select r/w 0 - destination of the sa7 nation bit is not the data link interface. 1 - destination of the sa7 national bit is the data link interface. 5 receive sa6 data link select r/w 0 - destination of the sa6 nation bit is not the data link interface. 1 - destination of the sa6 national bit is the data link interface. 4 receive sa5 data link select r/w 0 - destination of the sa5 nation bit is not the data link interface. 1 - destination of the sa5 national bit is the data link interface. 3 receive sa4 data link select r/w 0 - destination of the sa4 nation bit is not the data link interface. 1 - destination of the sa4 national bit is the data link interface.
xrt84l38 429 rev. 1.0.1 octal t1/e1/j1 framer the common channel signaling (ccs) messages are actually data link information applicable to all thirty-two timeslots of an e1 frame, thus the name common channel signaling. the receive signaling and data link control [2:0] bits of the receive signaling and data link select register (rsdlsr) determine if timeslot octet will be used to carry data link information or cas signals. the table below shows configuration of the receive signaling and data link control [2:0] bits of the receive signaling and data link select register (rsdlsr). if the receive signaling and data link select [2:0] bits of the receive signaling and data link select register are set to 1xx, the data link interface becomes destination of the timeslot 16 octet. 14.2.4 how to configure xrt84l38 to receive data link information through d or e channels the xrt84l38 can configure any one or ones of the thirty-two e1 channels to be d or e channels except for channel number 0. d channel is used primarily for data link applications. e channel is used primarily for signaling for circuit switching with multiple access configurations. the receive conditioning select [3:0] bits of the receive channel control register (rccr) of each channel determine whether that particular channel is configured as d or e channel. these bits also determine what type of data or signaling conditioning is applied to each channel. if the receive conditioning select [3:0] bits of the receive channel control register of a particular timeslot are set to 1111, that timeslot is configured as a d or e timeslot. n ote : timeslot 0 can never be configured as d or e timeslot. 14.2.5 receive bos (bit oriented signaling) processor the receive bos processor handles receiving and processing of bos messages through the e1 data link channel. it generates receive end of transfer (rxeot) interrupt each time a bos message is received and stores the bos message into the receive message buffer. please see section ? for how to configure the bos processor block to receive bos message. 14.2.6 receive lapd controller the receive lapd controller implements the message-oriented protocol based on itu recommendation q.921 link access procedures on the d-channel (lapd) type of protocol. it provides the following functions: ? zero deletion receive signaling and data link select register (rsdlsr) (indirect address = 0xn0h, 0x0ch) b it n umber b it n ame b it t ype b it d escription 2-0 receive signaling and data link select r/w 000 - timeslot 16 octet is extracted directly to the receive serial output interface through the rxser_n pin. 001 - timeslot 16 octet is extracted directly to the receive overhead out - put interface through the rxoh_n pin or the receive signaling control register of timeslot 16. 010 - timeslot 16 octet is extracted directly to the receive serial output interface through the rxser_n pin. 011 - timeslot 16 octet is extracted directly to the receive overhead out - put interface through the rxoh_n pin or the receive signaling control register of timeslot 16. 1xx - timeslot 16 octet is extracted to the data link interface. receive channel control register (rccr) (indirect address = 0xn2h, 0x60h - 0x7fh) b it n umber b it n ame b it t ype b it d escription 3-0 receive condition - ing select r/w 1111 - this c hannel is configured as d or e timeslot.
xrt84l38 430 octal t1/e1/j1 framer rev. 1.0.1 ? pattern recognition for idle flag detection ? pattern recognition for abort sequence detection ? frame check sequence verification ? t1 receiver interface ? receive data link message buffer access two 96-byte buffers in shared memory are allocated for receive lapd controller to reduce the frequency of microprocessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt. there are no restrictions on the length of the message received. however, the 96-byte buffer is deep enough to hold one entire lapd path or test signal identification message. please see section ? for how to configure the receive lapd controller to receive and extract mos messages.
xrt84l38 431 rev. 1.0.1 octal t1/e1/j1 framer 15.0 transmit liu interface the purpose of the transmit liu interface is to take the outbound frame data from the transmit framer block and to do the following: ? to encode the outbound frame data into any one of the following formats ? single-rail (e.g., a binary data stream) ? dual-rail, ami line code ? dual rail, hdb3 line code ? to output this encoded data to an liu device via the txpos, txneg and txlineclk output pins. 16.0 receive liu interface the purpose of the receive liu interface is to receive either single-rail or dual-rail data from an liu ic and to do the following: ? decode this incoming data from the single-rail, ami or hdb3 line code and convert it into a binary data stream ? route this binary data stream to the receive framer block ? detect and declare the loss of signal condition.
xrt84l38 432 octal t1/e1/j1 framer rev. 1.0.1 ordering information p art n umber p ackage o perating t emperature r ange xrt84l38 388 pin plastic ball grid array -40 0 c to +85 0 c package dimensions 388 pin plastic ball grid array (35 x 35 mm pbga) rev. 1.0 (bottom view) a1 c a2 d2 b a symbol millimeters min max inches min max a1 0.028 0.020 a2 0.051 0.039 b 0.035 0.024 d1 1.250bsc c 1.27bsc 0.050bsc 0.70 0.50 1.30 1.00 0.90 0.60 31.75bsc note: the control dimension is the millimeter column d 1.386 1.370 35.20 34.80 0.016 0.028 0.40 0.70 d2 1.185 1.177 30.10 29.90 a 0.106 0.075 2.70 1.90 e a b c d e f g h j k l m n p r t u v w y aa ab ac ad ae af 26 1 3 5 7 9 11 13 15 17 19 21 23 25 2 4 6 8 10 12 14 16 18 20 22 24 e d1 d b e d1 d chamfer optional mp
xr xrt84l38 octal t1/e1/j1 framer rev. 1.0.1 433 notice exar corporation reserves the right to make changes to the products contained in this publication in order to improve design, performance or reliability. exar corporation assumes no responsibility for the use of any circuits described herein, conveys no license under any patent or other right, and makes no represen- tation that the circuits are free of patent infringement. charts and schedules contained here in are only for illustration purposes and may vary depending upon a user?s specific application. while the information in this publication has been carefully checked; no responsibility, however, is assumed for inaccuracies. exar corporation does not recommend the use of any of its products in life support applications where the failure or malfunction of the product can reasonably be expected to cause failure of the life support sys- tem or to significantly affect its safety or effectiveness. products are not authorized for use in such applica- tions unless exar corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury or damage has been minimized; (b) the user assumes all such risks; (c) potential liability of exar corpo- ration is adequately protected under the circumstances. copyright 2006 exar corporation datasheet september 2006. reproduction, in part or whole, without the prior written consent of exar corporation is prohibited. revisions rev. 1.0.0 - february 2004 - release to production rev. 1.0.1 - september 2006 - correction to table titles in the pin list, update with new logo.

▲Up To Search▲

Price & Availability of XRT84L38-L38PCI

	To Download XRT84L38-L38PCI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .